mcp-registry/com.medigami/mcp · v1.28.1
As of 2026-10-22 17:50 UTC, the Medigami MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 3 minutes.
Medigami: medical bill error scan, denial decoding, appeal deadlines, hospital price lookup
Claude Code
claude mcp add --transport http medigami-mcp-server https://mcp.medigami.com/public/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"medigami-mcp-server": {
"type": "http",
"url": "https://mcp.medigami.com/public/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
87 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
106 parameter(s) across 34 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Loading this server's tool list costs an agent ~17,777 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Handshake + tools/list takes ~1,556 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
83 of 87 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 34 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.medigami%2Fmcp/fixes
{
"name": "analyze_glp1_pathways",
"description": "Find all access pathways for a GLP-1 drug (Ozempic, Wegovy, Mounjaro, Zepbound) given patient eligibility factors. Ranks pathways by monthly cost, flags prior-authorization rules and step-therapy, and returns the recommended appeal strategy if denial is likely.\n\nWHEN TO USE: User specifically asks about GLP-1 drugs (Ozempic, Wegovy, Mounjaro, Zepbound) — coverage, prior-auth strategy, step-therapy alternatives.\n\nWHEN NOT: For non-GLP-1 prescriptions (use optimize_prescription).",
"inputSchema": {
"type": "object",
"required": [
"insurer",
"bmi"
],
"properties": {
"bmi": {
"type": "number"
},
"state": {
"type": "string"
},
"has_cvd": {
"type": "boolean"
},
"insurer": {
"type": "string"
},
"medicare": {
"type": "boolean"
},
"has_diabetes": {
"type": "boolean"
},
"current_copay": {
"type": "number"
},
"tried_step_therapy": {
"type": "array",
"items": {
"type": "string"
},
"description": "Drug names already tried under step therapy, e.g. ['metformin']."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "appeal_escalation_path_finder",
"description": "[Taxonomy VII.129 — baseline response (public data only)] Find the correct escalation path for a denied claim (internal appeal → external review → DOI).\n\nWHEN TO USE: User needs to know the deadlines and agencies for each step of appealing a denial. Pass state (e.g. 'CA') and insurer for state-specific and insurer-specific values.\n\nWHEN NOT: Without state/insurer — still works but returns generic federal defaults. Follow up with state for best answer.\n\nEXAMPLES:\n- CA / UnitedHealthcare escalatio",
"inputSchema": {
"type": "object",
"properties": {
"state": {
"type": "string",
"description": "Two-letter US state code. State-specific external-review deadlines and DOI agency URL are returned when we have them (top 16 states)."
},
"insurer": {
"type": "string",
"description": "Insurer canonical name, e.g. 'UnitedHealthcare', 'Aetna'. Used to look up payer-specific appeal windows."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "billing_charge_vs_allowed_delta",
"description": "[Taxonomy III.51 — baseline response (public data only)] Delta between billed charge and payer-allowed amount for a claim line.\n\nWHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable.\n\nWHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.",
"inputSchema": {
"type": "object",
"required": [
"billed_usd",
"allowed_usd"
],
"properties": {
"billed_usd": {
"type": "number"
},
"allowed_usd": {
"type": "number"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.medigami/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.medigami/mcp"}) over MCP.
submit_denial_letter ~390 tokensgenerate_appeal_letter ~387 tokensformat_citation ~299 tokensbill_shock_predictor ~295 tokensformat_medigami_citation ~273 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.medigami%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.medigami%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.medigami%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.medigami%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.medigami%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:9db741af4864532f…, first seen 2026-10-17, included at leaf 15209 of 47,320. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge servers · most reliable ml servers · most reliable finance servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 17:50 UTC, the Medigami MCP server is up with a Glimind reliability score of 81/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 14 outages in 90 days, with a median recovery of 3 minutes.
Medigami MCP server advertises 87 tools, including analyze_glp1_pathways, appeal_argument_generator, appeal_escalation_path_finder, appeal_success_predictor, batch_scan_bills.
Point your MCP client at this streamable-http endpoint: https://mcp.medigami.com/public/mcp
Glimind scanned all 87 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.