Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
MedBillAnalyzer is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
7
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Compares a medical bill with the insurer's Explanation of Benefits and lists where they disagree.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http medbillanalyzer-mcp 'https://app.medbillanalyzer.com/mcp/apps?via=mcp_registry'
# 2 — ask your agent for something these tools do
# check_medical_bill, get_case, unlock_case and 4 more
MedBillAnalyzer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MEAll 1 server
medbillanalyzer1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http medbillanalyzer-mcp 'https://app.medbillanalyzer.com/mcp/apps?via=mcp_registry'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| bill_document | object | no | The bill as a file, read for you. Use this when you have the document itself — a photo, a scan, or a PDF from the provider’s portal. Send it one of three ways: data_base64 if you have the bytes; `up |
| eob_document | object | no | The Explanation of Benefits as a file, read for you. It usually sits behind the insurer’s login, which is what upload_id is for. Send it one of three ways: data_base64 if you have the bytes; `uplo |
| bill | object | no | The bill already transcribed into structured form. Prefer bill_document when you can send the file itself or a link to it: the transcription is then done by a reader tuned for these forms and checke |
| eob | object | no | A single Explanation of Benefits, already transcribed. |
| eobs | array | no | Every Explanation of Benefits covering this bill, already transcribed. Use this rather than eob whenever there is more than one — a hospital statement usually spans several claims and each claim has |
| good_faith_estimate | string | no | The total on the written Good Faith Estimate the provider gave the patient before the care, as printed — "$1,204.37". Needed for the self-pay check: under the No Surprises Act a self-pay bill that com |
| label | string | no | A short human label for this case. |
Retrieve a case by id. Returns the same free summary, plus every finding in detail once the case has been unlocked.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | string | yes | — |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | string | yes | — |
| plan | string | no | "one_bill" is $10 for this bill, charged once. "subscription" is the monthly membership, which unlocks up to 25 bills a calendar month for anyone in a household. It is sold only while the case summary |
| shared_payment_token | string | no | A Stripe Shared Payment Token (spt_…) granted to the stripe_profile in the case summary's purchase, for at least $10.00 USD. When present, this call charges it once and unlocks the case; no chec |
| membership_token | string | no | An existing membership. If the user already subscribed, pass the token they were given and this bill unlocks immediately with nothing charged — a membership covers up to 25 bills a calendar month, inc |
Get the dispute letter and the phone script for an unlocked case. The letter is a template the patient sends in their own name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | string | yes | — |
| patient_name | string | yes | As it should appear on the letter. |
| account_number | string | no | — |
| provider_address_lines | array | no | — |
| include_pdf | boolean | no | Also return the letter as a print-ready PDF (base64). One page where it fits, addressed for a #10 window envelope, with fold marks. |
| reply_to_lines | array | no | Where the provider should write back. |
| letter_date | string | no | The date to print on the letter, as MM/DD/YYYY. Send the USER's local date: the server runs in UTC, so without this a patient in a western timezone can be handed a letter dated tomorrow, and it is the |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | string | yes | — |
| delete_token | string | yes | The one-time token returned by check_medical_bill. Deleting is a separate capability from reading on purpose: a case link can end up in a browser history or a forwarded message, and whoever finds it s |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | string | yes | — |
| outcome | string | yes | corrected the charge was removed in full; reduced some of it came off; refused they said no; ignored no reply at all; waiting sent but nothing back yet; not_sent the patient decided not to |
| amount_written_off | string | no | What the provider actually took off the bill, as printed — "$412.30". The one number that says whether any of this works. Omit if nothing came off or it is not known yet. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| case_id | string | yes | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install MedBillAnalyzer or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish MedBillAnalyzer can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.