MedaRep MCP server
com.medarep/medarepmedarep.comstreamable-httpv0.6.0Scanned
Surgeon and procedure-market intelligence for medical device reps, from public federal data.
38 tools: 5 can delete or cancel things, 31 change things and 2 only read.
- Reads private data · 2
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MedaRep MCP server can do
The MedaRep MCP server is published by medarep.com, a domain the MCP Registry verified. It has 38 tools. It can delete or cancel things (5 tools: update_list_item, set_account_status, my_customers, set_my_lines and 1 more) and create or change data (31 tools: coverage, glossary, rank_territory, new_surgeons and 27 more). 2 tools only read.
2 tools read private data (my_lists and log_visit).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
38 tools
Deletes or cancels 5Claude Code: deny
my_customersThe surgeons the rep already sells to, which warm_paths starts from.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it The surgeons the rep already sells to, which warm_paths starts from. Give an npi to mark that surgeon a customer, or an npi with customer false to unmark them; omit both to list them.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
save_territorySave a territory on the rep's MedaRep account from a metro, county FIPS codes and/or ZIP codes, optionally with its procedure family; it then shows under /territories and in my_ter…No findings
Why it is in this group
- The name "save_territory" says "save": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Save a territory on the rep's MedaRep account from a metro, county FIPS codes and/or ZIP codes, optionally with its procedure family; it then shows under /territories and in my_territories. Saving under an existing territory's name replaces it. The plan limits how many territories are kept. Use only when the user asks to save one.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
set_account_statusSet where a surgeon stands in a product segment: target, contacted, trialing, using_us, competitor (with which competitor, if known), lost, passed or unknown.No findings
Why it is in this group
- The name "set_account_status" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Set where a surgeon stands in a product segment: target, contacted, trialing, using_us, competitor (with which competitor, if known), lost, passed or unknown. A surgeon can be a customer in one segment and a target in another (using us for sports medicine, not yet for shoulder), so name the segment when the rep does; omit it for the surgeon in general. With using_us, share says how much of their cases in the segment the rep has (some, half, most, all): a customer at some or half is room to grow. using_us also marks them a customer (warm paths start from them); lost from using_us unmarks them unless another segment is still using us. Every change is kept in the history. Shared with the rep's team.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
set_my_linesAdd a company the rep sells, optionally narrowed to some of its brands (e.g.No findings
Why it is in this group
- The name "set_my_lines" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Add a company the rep sells, optionally narrowed to some of its brands (e.g. company "Stryker", brands ["Triathlon", "Mako"]); saving a company again replaces its brands, and none means the whole company. With remove true, drop that company. Use only when the user says what they sell.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
update_list_itemSet where a listed surgeon stands (target, contacted, trialing, using_us, competitor, lost, passed) or add a note to their thread, e.g.No findings
Why it is in this group
- The name "update_list_item" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Set where a listed surgeon stands (target, contacted, trialing, using_us, competitor, lost, passed) or add a note to their thread, e.g. after a call. The stage is the account's own, for the surgeon in general: it reads the same on every list and the profile, and set_account_status sets it for one product segment. using_us (or its old name, customer) also marks them as the rep's customer for warm_paths; moving off it unmarks them.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 31Claude Code: ask
add_noteKeep a note on a surgeon's account record that is not a visit: who decides, what they prefer, when to catch them, what a staff member said.No findings
Why it is in this group
- The name "add_note" says "add": a word for a change.
Description, as the server wrote it Keep a note on a surgeon's account record that is not a visit: who decides, what they prefer, when to catch them, what a staff member said. Shared with the rep's team like visits, sent to a connected HubSpot as a note on the contact, and read back with the record (changes_since). For something that happened with the surgeon on a day, use log_visit and its note. Notes that read like patient information are refused.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
changes_sinceWhat changed for one surgeon since the rep last touched them (their last logged visit, status change or note; or since a given day, default 90 days): moves and practice changes, pa…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it What changed for one surgeon since the rep last touched them (their last logged visit, status change or note; or since a given day, default 90 days): moves and practice changes, partners who joined or left, a new Open Payments year and any change of main company, a new Medicare year with the case change, and new FDA clearances and recalls from the companies engaged with them. With the rep's own record: status per line, recent visits, open follow-ups and notes. The first half of a pre-call brief; counts as opening the profile.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
company_profileA device company by name or slug: FDA 510(k), De Novo and PMA decisions by family and year, recalls (open first, by class), adverse-event trend against each family's category over …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A device company by name or slug: FDA 510(k), De Novo and PMA decisions by family and year, recalls (open first, by class), adverse-event trend against each family's category over two closed years, and consolidated financials for public parents. Needs the product and company coverage add-on; without it the answer is a notice.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
competitor_scorecardDevice companies scored against the others in a procedure family on innovation pace (new FDA decisions, market entries), recall and report signals (recalls, MAUDE reports above the…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Device companies scored against the others in a procedure family on innovation pace (new FDA decisions, market entries), recall and report signals (recalls, MAUDE reports above the category), commercial momentum (share of the family's Medicare cases through surgeons they engage, this year against last) and financial capacity, with a position: Leader, Innovator, Commercial mover or Fewer engaged surgeons. Give a family for its landscape, a company for its families, or both. Needs the product and company coverage add-on.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
coverageStates loaded, procedure family keys by market segment, DME and prescribing categories, data years, and the caller's plan limits.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it States loaded, procedure family keys by market segment, DME and prescribing categories, data years, and the caller's plan limits.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
cross_sellMore business in the accounts the rep already has: for each of their customers (marked on MedaRep), the procedures they do that one of the rep's lines covers (my_lines) where that …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it More business in the accounts the rep already has: for each of their customers (marked on MedaRep), the procedures they do that one of the rep's lines covers (my_lines) where that line's company is not already the one most engaged with them for those products, with their Medicare cases, who engages them for those products now and how deeply, and why it ranks. Give one customer's NPI for theirs, or none for the best across all customers. Needs saved lines and marked customers.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
facility_profileA hospital or ASC by CMS certification number: payer mix, inpatient DRG and outpatient procedure volumes, ASC case counts, negotiated commercial and Medicare Advantage prices for t…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A hospital or ASC by CMS certification number: payer mix, inpatient DRG and outpatient procedure volumes, ASC case counts, negotiated commercial and Medicare Advantage prices for the families done there, and who operates there.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
family_coverageA procedure family's device landscape: the FDA product codes behind it, clearances in the last 24 months by firm, open recalls, and the category's adverse-event trend by firm.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A procedure family's device landscape: the FDA product codes behind it, clearances in the last 24 months by firm, open recalls, and the category's adverse-event trend by firm. Needs the product and company coverage add-on; without it the answer is a notice.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
glossaryDefinitions of the published metrics: unit, source, reported or estimated, caveat, backtested accuracy, and the current data year.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Definitions of the published metrics: unit, source, reported or estimated, caveat, backtested accuracy, and the current data year. Cite these when explaining a number.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
handle_reasonRecord what the rep did about a surgeon's reasons from my_day: called (off the list for 90 days), not_now (30 days) or not_relevant (for good).No findings
Why it is in this group
- The name "handle_reason" says "handle": a word for a change.
Description, as the server wrote it Record what the rep did about a surgeon's reasons from my_day: called (off the list for 90 days), not_now (30 days) or not_relevant (for good). A new kind of reason brings the surgeon back. For a call or visit that happened, also log it with log_visit.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
incumbentsWhich device companies engage a territory's surgeons for a family and how deeply, surgeons open or lunch-only (no company over $500), independent-channel candidates, employment mix…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Which device companies engage a territory's surgeons for a family and how deeply, surgeons open or lunch-only (no company over $500), independent-channel candidates, employment mix, where cases are done (hospital, ASC, office) and the main sites of care.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
log_visitRecord a visit with a surgeon on the rep's account: a case covered, a meeting, a call, an in-service or a meal, on a date (default today), with an optional short note and the facil…Reads private data1 finding
Why it is in this group
- The name "log_visit" says "log": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe description's first sentence says "meeting": it reads calendars.
Findings
- Warn
The server marks "log_visit" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "log_visit" says "log": a word for reading.
Description, as the server wrote it Record a visit with a surgeon on the rep's account: a case covered, a meeting, a call, an in-service or a meal, on a date (default today), with an optional short note and the facility's CCN. Shared with the rep's team as customers are. Notes that read like patient information are refused with the reason; a meal comes back with a reminder about Open Payments reporting. Use when the rep tells you about a visit, after reading back what you will save.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_outlookA family's market in a place: Medicare cases by year, the all-Medicare estimate, the forecast to 2030 with ranges, the 65+ population and its growth, and per-metro or per-county su…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A family's market in a place: Medicare cases by year, the all-Medicare estimate, the forecast to 2030 with ranges, the 65+ population and its growth, and per-metro or per-county supply, access and demand index.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
my_accountsEvery account the rep (and their team) has logged: where it stands per product segment, the share of a customer's cases held and the room to grow, when it was last touched, and the…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Every account the rep (and their team) has logged: where it stands per product segment, the share of a customer's cases held and the room to grow, when it was last touched, and the next follow-up. Filter by status or by days untouched; sort=room puts the customers with the most cases not yet won first. Use it for a pipeline review, a list of neglected accounts, or where to expand.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
my_dayThe rep's day, as the site's Today page has it: follow-ups due, then the surgeons with a reason to call across their saved territories, their own accounts and what is new this week…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The rep's day, as the site's Today page has it: follow-ups due, then the surgeons with a reason to call across their saved territories, their own accounts and what is new this week first, each with why and the step to take. Start a morning or a route plan here. Counts toward the plan's daily territories like opening Today.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
my_follow_upsThe rep's open follow-ups (and their team's), soonest first, overdue flagged; until (YYYY-MM-DD) limits them to what is due by then, e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The rep's open follow-ups (and their team's), soonest first, overdue flagged; until (YYYY-MM-DD) limits them to what is due by then, e.g. the end of this week.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
my_linesThe companies the rep sells, each whole or narrowed to some brands, with the procedure families those brands cover.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The companies the rep sells, each whole or narrowed to some brands, with the procedure families those brands cover. Other tools read these to mark switches won or lost, the rep's own recalls and their scorecard rows.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
my_territoriesThe territories the rep drew and saved on MedaRep, each with a place (metro, counties, zips) to pass to rank_territory, incumbents, switching and the other territory tools, and its…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The territories the rep drew and saved on MedaRep, each with a place (metro, counties, zips) to pass to rank_territory, incumbents, switching and the other territory tools, and its family when one was saved.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
new_clearancesA procedure family's new FDA 510(k), De Novo and PMA decisions from the last days (default 90), read weekly from FDA: each as a new entrant (the company's first here), a new system…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A procedure family's new FDA 510(k), De Novo and PMA decisions from the last days (default 90), read weekly from FDA: each as a new entrant (the company's first here), a new system (a name it has not cleared before) or a line extension (more of a line it already sells), with the basis, what it means for the rep (soWhat, from their side when the company is one of their lines) and FDA's page. Optionally one company. Needs the product and company coverage add-on.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
new_surgeonsSurgeons in a place the Medicare files cannot show yet: fellows who stayed (paid the assistant-at-surgery fee, now practising here) and recent joins of established groups.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Surgeons in a place the Medicare files cannot show yet: fellows who stayed (paid the assistant-at-surgery fee, now practising here) and recent joins of established groups. Each with its evidence and the signal's backtested accuracy.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
opportunitiesA territory's surgeons ranked by dated reasons they may be worth a call now: a recall or rising MAUDE reports at a company engaged with them for these products (possible supply or …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A territory's surgeons ranked by dated reasons they may be worth a call now: a recall or rising MAUDE reports at a company engaged with them for these products (possible supply or service disruption, not a finding of fault), a new FDA clearance for their main company (read as new entrant, new system or line extension), engagement moving to a different main company, a move or practice change, a new surgeon not in the Medicare files yet, a growing practice with no device ties. Each with its evidence, a warm introduction from the rep's customers if one exists, the lists it is already on, and a next step. Give a saved territory by name (its family is used unless one is given) or a family and a place; since (YYYY-MM-DD, default a year ago) keeps the reasons recent, e.g. the date of the last brief. Recall, clearance and switching reasons need the coverage add-on.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
ownership_changesDated deals that changed who sells device products: acquisitions, mergers, carve-outs (Stryker's US spinal implants to VB Spine), spin-offs and renames, each in a sentence with wha…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Dated deals that changed who sells device products: acquisitions, mergers, carve-outs (Stryker's US spinal implants to VB Spine), spin-offs and renames, each in a sentence with what it means for a rep and its source. Filter by company (as asked, as it reported, or its owner now), procedure family (companies with FDA decisions in it) and since (YYYY-MM-DD). With a family and a place, each deal counts the surgeons there the company that changed hands engaged in the three years before it, naming the busiest the plan shows.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
practice_profileA PECOS group practice by PAC ID: size, employment model and who decides, Medicare cases by family with its top surgeons, device payments by company, and sites.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A PECOS group practice by PAC ID: size, employment model and who decides, Medicare cases by family with its top surgeons, device payments by company, and sites.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
rank_territorySurgeons operating in a place for a procedure family, ranked by Medicare cases weighted by how deep their payment ties to a device company are: cases and change, MA-adjusted trend,…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Surgeons operating in a place for a procedure family, ranked by Medicare cases weighted by how deep their payment ties to a device company are: cases and change, MA-adjusted trend, practice and employment, likely incumbent (the company most engaged with them, by Open Payments) and relationship depth, payments, sites of care, and all-payer estimates where the plan includes them.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
save_to_listAdd surgeons by NPI to one of the rep's prospect lists (by id or name), or make a new list with them when no list matches.No findings
Why it is in this group
- The name "save_to_list" says "save": a word for a change.
Description, as the server wrote it Add surgeons by NPI to one of the rep's prospect lists (by id or name), or make a new list with them when no list matches. Use when the user asks to save targets from rank_territory, new_surgeons or warm_paths. The plan limits how many lists; up to 500 surgeons each.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
set_follow_upAdd a follow-up for a surgeon, due by a day (what to do, without patient information); close one with done and its id from my_follow_ups; or move one to another day or reword it wi…No findings
Why it is in this group
- The name "set_follow_up" says "set": a word for a change.
Description, as the server wrote it Add a follow-up for a surgeon, due by a day (what to do, without patient information); close one with done and its id from my_follow_ups; or move one to another day or reword it with move, its id, and the new due or what.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
surgeon_profileOne clinician by NPI: Medicare cases by family and trend, cases under CMS's floor, forecast, peers, device payments by company and depth, research, practice and who decides, billin…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it One clinician by NPI: Medicare cases by family and trend, cases under CMS's floor, forecast, peers, device payments by company and depth, research, practice and who decides, billing groups, sites, partners, movement, DME ordered, device-pointing prescribing, academic record, and the new-surgeon signal. Counts as a profile view on the caller's plan.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
switchingSurgeons in a territory whose main device company for a family (the one most engaged with them for its products) changed between the last two Open Payments years: who, from whom, t…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Surgeons in a territory whose main device company for a family (the one most engaged with them for its products) changed between the last two Open Payments years: who, from whom, to whom, with their Medicare cases, plus new and ended ties. Needs the product and company coverage add-on.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
territory_changesRecent moves and practice changes among a territory's surgeons, and surgeons whose Medicare cases are placed here but who practise elsewhere now.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Recent moves and practice changes among a territory's surgeons, and surgeons whose Medicare cases are placed here but who practise elsewhere now.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
warm_pathsWhich of the rep's own customers (marked on MedaRep) can open a door to a surgeon: partners now or before, the same hospital, the same device company, or a partner in common, with …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Which of the rep's own customers (marked on MedaRep) can open a door to a surgeon: partners now or before, the same hospital, the same device company, or a partner in common, with each path's strength. Give one NPI, or a family and a place for the territory's warmest targets and its lookalikes: surgeons who fit the pattern of the rep's customers there (setting, employment, volume, company), connected or not.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
who_ordersClinicians ranked by referred DME a supplier billed (bracing, bone growth stimulators, CGM, pumps, NPWT, dressings, compression, CPAP, CPM) or by device-pointing prescribing (rx-in…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Clinicians ranked by referred DME a supplier billed (bracing, bone growth stimulators, CGM, pumps, NPWT, dressings, compression, CPAP, CPM) or by device-pointing prescribing (rx-insulin, rx-anticoagulant, rx-bph, rx-glaucoma, rx-overactive-bladder), with specialty mix.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
my_listsThe rep's prospect lists on MedaRep with counts by status, or one list (by id or name) with where each surgeon stands (target, contacted, trialing, using_us, competitor, lost, pass…Reads private dataNo findings
Why it is in this group
- The name "my_lists" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Description, as the server wrote it The rep's prospect lists on MedaRep with counts by status, or one list (by id or name) with where each surgeon stands (target, contacted, trialing, using_us, competitor, lost, passed: the account's own stage, the same on every list), note, practice and latest Medicare cases.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
searchSearch by name.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Search by name. Returns surgeons (npi), practices (pacId), hospitals and ASCs (ccn), device companies (company slug), states, metros (metro code) and counties (FIPS), for use in the other tools.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:19 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 36
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://medarep.com/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://medarep.com/api/auth
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 36 tools that change things (5 destructive, 31 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://medarep.com/api/mcp: tools/list returned 38 tools to an anonymous client, including update_list_item (destructive), set_account_status (destructive), my_customers (destructive), set_my_lines (destructive), save_territory (destructive) and 31 more
Findings
Matches of fixed checks, with the text they matched.
- Warnlog_visit
The server marks "log_visit" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "log_visit" says "log": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http medarep https://medarep.com/api/mcpclaude mcp add --transport http medarep https://medarep.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__medarep__search",
"mcp__medarep__my_lists"
],
"ask": [
"mcp__medarep__coverage",
"mcp__medarep__glossary",
"mcp__medarep__rank_territory",
"mcp__medarep__new_surgeons",
"mcp__medarep__territory_changes",
"mcp__medarep__incumbents",
"mcp__medarep__market_outlook",
"mcp__medarep__surgeon_profile",
"mcp__medarep__practice_profile",
"mcp__medarep__facility_profile",
"mcp__medarep__who_orders",
"mcp__medarep__warm_paths",
"mcp__medarep__cross_sell",
"mcp__medarep__company_profile",
"mcp__medarep__family_coverage",
"mcp__medarep__new_clearances",
"mcp__medarep__ownership_changes",
"mcp__medarep__competitor_scorecard",
"mcp__medarep__switching",
"mcp__medarep__opportunities",
"mcp__medarep__save_to_list",
"mcp__medarep__log_visit",
"mcp__medarep__set_follow_up",
"mcp__medarep__add_note",
"mcp__medarep__my_follow_ups",
"mcp__medarep__my_day",
"mcp__medarep__handle_reason",
"mcp__medarep__my_accounts",
"mcp__medarep__changes_since",
"mcp__medarep__my_lines",
"mcp__medarep__my_territories"
],
"deny": [
"mcp__medarep__update_list_item",
"mcp__medarep__set_account_status",
"mcp__medarep__my_customers",
"mcp__medarep__set_my_lines",
"mcp__medarep__save_territory"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as medarep. Review it before you use it.
Capability tags behind 2 rules
- mcp__medarep__my_lists private-data
- mcp__medarep__log_visit private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.medarep/medarep/verify?hash=36a26aebc17fa0e77eeeb862ed70177eca294625fc35081d150c7dd932b0ca9d" | jq -e '.changed == false'Pinned hash 36a26aebc17f, from Nov 20, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.medarep/medarep/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.medarep/medarep)Source: MCP Registry. Synced Nov 20, 2026, 05:17 UTC.
MedaRep MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MedaRep MCP server safe?
- No scan can promise that. What its definitions show: 38 tools, 36 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MedaRep MCP server delete data?
- Yes. 5 tools can delete, cancel or revoke something: update_list_item, set_account_status, my_customers, set_my_lines and save_territory.
Can the MedaRep MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MedaRep MCP server have?
- 38 tools: 5 destructive, 31 write, 2 read. update_list_item, set_account_status, my_customers, set_my_lines, save_territory, coverage, glossary, rank_territory and 30 more.
Does the MedaRep MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MedaRep MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MedaRep MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.