MedBillAnalyzer MCP server
com.medbillanalyzer/medbillanalyzermedbillanalyzer.comstreamable-httpv0.1.2Scanned
Compares a medical bill with the insurer's Explanation of Benefits and lists where they disagree.
7 tools: 1 can delete or cancel things, 1 do something that can't be undone, 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. 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 MedBillAnalyzer MCP server can do
The MedBillAnalyzer MCP server is published by medbillanalyzer.com, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (1 tool: delete_case), do things that cannot be undone, such as sending, paying or publishing (unlock_case) and create or change data (3 tools: check_medical_bill, report_outcome and export_case). 2 tools only read.
2 tools bring in text other people can write (check_medical_bill and unlock_case); 1 tool can send data out of your system (check_medical_bill).
The fixed checks matched 3 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 0.1.2.
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.
7 tools
Deletes or cancels 1Claude Code: deny
delete_caseDelete everything held about a case, immediately and permanently.No findings
Why it is in this group
- The name "delete_case" says "delete": a word for removing or ending something.
- The description says "cannot be recovered".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete everything held about a case, immediately and permanently. The record is removed, not flagged, and it cannot be recovered afterwards — not by us either. This is the promise the privacy policy makes, and it needs no account. It does need the delete token issued when the case was created: reading a case and destroying it are deliberately different capabilities.
Annotations the server declares
- title: Delete a case
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Can't be undone 1Claude Code: ask
unlock_casePay to unlock the full findings, the dispute letter and the phone script.Reads text others writeNo findings
Why it is in this group
- The name "unlock_case" says "unlock": a word for a change.
- The description's first verb is "pay": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Pay to unlock the full findings, the dispute letter and the phone script. With a `shared_payment_token` (a Stripe Shared Payment Token granted to the `stripe_profile` in the case summary's `purchase`), it charges $10.00 for this bill and unlocks the case in the same call. Without one, it returns a checkout URL and charges nothing itself. A case with no findings is refused: there is nothing to buy, and the user pays nothing when nothing is found. So is a case with nothing to act on yet (`nothing_to_act_on`), such as a bill sent without its Explanation of Benefits whose only finding is that the EOB is missing.
Annotations the server declares
- title: Unlock a case
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 3Claude Code: ask
check_medical_billCompare a medical bill against the Explanation of Benefits the patient’s insurer issued for the same care, and report where the two disagree.Reads text others writeCan send data out3 findings
Why it is in this group
- The description's first verb is "compare": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.bill_document.url): a request to a URL can carry data to whoever runs it.
Findings
- Info
The input schema at properties.bill_document.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bill_document.properties.url.description: "...r a redirect, and so are links carrying credentials. At most 3 redirects, 12 MB, 20 seconds..."
- Info
The input schema at properties.eob_document.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.eob_document.properties.url.description: "...r a redirect, and so are links carrying credentials. At most 3 redirects, 12 MB, 20 seconds..."
- Warn
The server marks "check_medical_bill" 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":true}; The description's first verb is "compare": a word for reading.
Description, as the server wrote it Compare a medical bill against the Explanation of Benefits the patient’s insurer issued for the same care, and report where the two disagree. Use when someone shares a medical bill, hospital statement, doctor bill, lab bill or EOB and asks whether it is correct, what they actually owe, or how to dispute it. The bill is required; the EOB is strongly recommended and is what makes most of the checks possible. If you can see the documents but cannot attach their bytes, transcribe them into `bill` and `eobs` exactly as printed. Free: returns a summary and the title of every finding, but not the detail behind them.
Annotations the server declares
- title: Check a medical bill
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
export_caseEverything stored about a case, as JSON, in one response.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 Everything stored about a case, as JSON, in one response. This is the portable copy the privacy policy offers. It is deliberately the whole record rather than a summary, so that what is returned here can be compared against what the policy says is kept.
Annotations the server declares
- title: Export a case
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
report_outcomeRecord what happened after the patient sent the dispute letter: corrected, reduced, refused, ignored, still waiting, or not sent.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.
Description, as the server wrote it Record what happened after the patient sent the dispute letter: corrected, reduced, refused, ignored, still waiting, or not sent. Free. Every answer counts equally, and it is kept only as an aggregate count — nothing about it is stored against the case. This product can tell that two documents disagreed; only these reports show whether saying so to a billing office changes anything.
Annotations the server declares
- title: Report what happened after the letter
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_caseRetrieve a case by id.No findings
Why it is in this group
- The name "get_case" says "get": a word for reading.
Description, as the server wrote it Retrieve a case by id. Returns the same free summary, plus every finding in detail once the case has been unlocked.
Annotations the server declares
- title: Read a case
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_case_outputsGet the dispute letter and the phone script for an unlocked case.No findings
Why it is in this group
- The name "get_case_outputs" says "get": a word for reading.
Description, as the server wrote it Get the dispute letter and the phone script for an unlocked case. The letter is a template the patient sends in their own name.
Annotations the server declares
- title: Get the dispute letter and phone script
- 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 private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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:42 UTC, unchanged since Oct 22, 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
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 1 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://app.medbillanalyzer.com/mcp/apps?via=mcp_registry: tools/list returned 7 tools to an anonymous client, including delete_case (destructive), unlock_case (irreversible), check_medical_bill (write), report_outcome (write), export_case (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_medical_bill" 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":true}; The description's first verb is "compare": a word for reading.
The input schema at properties.bill_document.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.bill_document.properties.url.description: "...r a redirect, and so are links carrying credentials. At most 3 redirects, 12 MB, 20 seconds..."
The input schema at properties.eob_document.properties.url.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.eob_document.properties.url.description: "...r a redirect, and so are links carrying credentials. At most 3 redirects, 12 MB, 20 seconds..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools6 changed.~6 changedView diff
- Changed:delete_caseDeletes or cancelsinputSchema
- Changed:export_caseChanges thingsinputSchema
- Changed:get_caseOnly readsinputSchema
- Changed:get_case_outputsOnly readsinputSchema
- Changed:report_outcomeChanges thingsinputSchema
- Changed:unlock_caseCan't be undoneinputSchema
Install
Pinned to version 0.1.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http medbillanalyzer https://app.medbillanalyzer.com/mcp/apps?via=mcp_registryclaude mcp add --transport http medbillanalyzer https://app.medbillanalyzer.com/mcp/apps?via=mcp_registryRun 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__medbillanalyzer__get_case",
"mcp__medbillanalyzer__get_case_outputs"
],
"ask": [
"mcp__medbillanalyzer__check_medical_bill",
"mcp__medbillanalyzer__unlock_case",
"mcp__medbillanalyzer__report_outcome",
"mcp__medbillanalyzer__export_case"
],
"deny": [
"mcp__medbillanalyzer__delete_case"
]
}
}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 medbillanalyzer. Review it before you use it.
Capability tags behind 2 rules
- mcp__medbillanalyzer__check_medical_bill untrusted-input, outbound
- mcp__medbillanalyzer__unlock_case untrusted-input
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.medbillanalyzer/medbillanalyzer/verify?hash=0251479cf05bf0f999d1a5653d41067382972969b9c4aba15930b2093dc366c6" | jq -e '.changed == false'Pinned hash 0251479cf05b, from Nov 13, 2026, 03:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.medbillanalyzer/medbillanalyzer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.medbillanalyzer/medbillanalyzer)Source: MCP Registry. Synced Nov 13, 2026, 03:17 UTC.
MedBillAnalyzer MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MedBillAnalyzer MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MedBillAnalyzer MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_case.
Can the MedBillAnalyzer MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: unlock_case.
What tools does the MedBillAnalyzer MCP server have?
- 7 tools: 1 destructive, 1 irreversible, 3 write, 2 read. delete_case, unlock_case, check_medical_bill, report_outcome, export_case, get_case and get_case_outputs.
Does the MedBillAnalyzer MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MedBillAnalyzer MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_medical_bill.
Has the MedBillAnalyzer MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.