MediBill Saver — medical bill audit tools
Server Details
Medicare rates, hospital quality, and dispute scenarios from six federal public-domain datasets.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.4/5 across 5 of 5 tools scored.
Each tool serves a distinct function: full audit, scenario detail, scenario listing, rate lookup, and hospital lookup. No overlap in purpose.
All tools use a consistent verb_noun pattern in snake_case (e.g., audit_medical_bill, lookup_cpt_rate), making them predictable and easy to differentiate.
Five tools is well-scoped for a focused medical bill audit domain, covering key operations without unnecessary clutter.
Covers core workflows (audit, dispute info, rate/hospital lookup). Minor gap: no tool for payment or retrieving full audit results after payment, but the preview suffices for initial interaction.
Available Tools
5 toolsaudit_medical_billAudit a medical bill against six federal data sourcesInspect
Runs a full audit on a medical bill — cross-references every charge against six federal data sources (CMS PFS, NADAC, HPT, NCCI, Hospital Compare, IRS Pub 78) and identifies potential billing errors plus the federal statutes the patient can cite. Returns a free preview (severity, totals, issue count). The full report with line-by-line breakdown and up to 5 ready-to-mail dispute letters requires payment ($19.97 single audit, or covered under Family/Pro subscription). Returns a unique unlock URL for completing payment.
| Name | Required | Description | Default |
|---|---|---|---|
| billText | Yes | Plain-text bill content. Include line items, charges, dates, hospital name if visible. Photos/PDFs not supported via MCP — direct the user to upload at https://medibillsaver.com/scan for image/PDF support. |
get_dispute_scenarioGet summary of a medical-bill dispute scenarioInspect
Returns a summary of one MediBill Saver dispute scenario: title, category, the federal statute backing the patient's right to dispute, and a link to the full scenario page (which contains the how-to-spot checklist and sample dispute language). Useful when a patient asks 'how do I dispute X' or 'what is HIPAA §164.524'. Free, no authentication required.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Scenario slug (e.g. 'upcoded-er-visit', 'duplicate-charges'). Use list_dispute_scenarios first if unsure. |
list_dispute_scenariosList all available dispute scenariosInspect
Returns the full index of dispute scenarios MediBill Saver covers — slug, title, category, and the federal statute. Useful to discover which scenarios exist before calling get_dispute_scenario. Free, no authentication required.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
lookup_cpt_rateLook up Medicare rate for a CPT/HCPCS codeInspect
Returns the Medicare national-average non-facility allowed amount for a CPT or HCPCS procedure code from the CMS Physician Fee Schedule. Useful for benchmarking what a hospital or clinic billed against what Medicare reimburses. Free, no authentication required. For the patient-facing description and disputes information, link the user to the returned pageUrl.
| Name | Required | Description | Default |
|---|---|---|---|
| cpt | Yes | 5-character CPT or HCPCS code, uppercase (e.g. '99285', 'J7030', 'G0008'). |
lookup_hospitalLook up a U.S. hospital by CCN or nameInspect
Returns hospital metadata from CMS data: name, location, ownership type, CMS overall rating (1-5 stars), and 501(c)(3) charity-care eligibility. Useful when a patient mentions a specific hospital and wants to know the facility's federally-published quality profile and whether charity care is available. Free, no authentication required.
| Name | Required | Description | Default |
|---|---|---|---|
| ccn | No | CMS Certification Number (Provider Number) — 6 character identifier (e.g. '050625'). | |
| name | No | Hospital name (partial match supported). Use when CCN is not known. | |
| state | No | Two-letter U.S. state code (e.g. 'CA'). Optional, narrows name search. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!