Health · Remote MCP server
Coverage Exception
Why Medicare Part D restricts a drug, and the exception and appeal path to challenge it.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.builtforai/coverage-exception- Version
- 1.0.0
- Status
- Active
- Category
- health
- Transport
- Streamable HTTP
- Published
- 2026-09-18
- Updated
- 2026-09-18
- Publisher
- builtforai (GitHub) · 5 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/builtforai) · how
- Website
- insurewith.ai/
- Repository
- github.com/builtforai/builtforai-healthcare
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://insurewith.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- builtforai-insurewith 1.0.0 · protocol 2024-11-05
- Tools discovered
- 2:
medicare_part_d_out_of_pocket_cap,medicare_coverage_restriction_and_exception - Checked on
- 2026-10-05
How to connect Coverage Exception
Coverage Exception is a remote MCP server: there is nothing to install. Its endpoint is https://insurewith.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from builtforai (GitHub)
| Server | Runs |
|---|---|
| Generic TimelineWhether a drug has a marketed generic today, and when its Orange Book protections lapse. | Remote · HTTPLive check: ✓ handshake |
| Loe ExposureDrug patent expiries ranked by the Medicare Part D spending exposed to them. | Remote · HTTPLive check: ✓ handshake |
| Part D CapMedicare Part D out-of-pocket cap: when you hit it, and what the payment plan changes. | Remote · HTTPLive check: ✓ handshake |
| Procedure CoverageMedicare coverage and fee-schedule amounts for CPT/HCPCS codes against a diagnosis. | Remote · HTTPLive check: ✓ handshake |
More health servers
| Server | Runs |
|---|---|
| Constat MCP - FDA Device Evidence LifecycleFDA and CMS evidence for AI medical devices: 510(k), postmarket, reimbursement, and compliance. | Remote · HTTPLive check: ✓ handshake |
| Convergent Provider DirectorySearch a healthcare provider directory and get full provider details by id. | Remote · HTTPLive check: ✓ handshake |
| Costkits MCPMCP server for CostKits: live healthcare procedure cost estimates and provider pricing. | Local · stdio |
| CounterScript - Drug Price BenchmarksFree US drug-price benchmarks from federal data (CMS NADAC): a benchmark, not a price anyone owes. | Remote · HTTPLive check: ✓ handshake |
| CredcycleProvider credentialing & payer-enrollment tracking for medical practices - read-only demo tools. | Remote · HTTPLive check: ✓ handshake |
| Cup24.it AvailabilitySearch private healthcare appointment availability across Cup24.it: services, doctors, clinics. | Remote · HTTPLive check: ✗ no handshake |
| Cure Cancer With AIFree oncology data (research, trials, FDA approvals, news) plus IBM MAMMAL biomedical predictions. | Remote · HTTPLive check: ✓ handshake |
| DailymedDailyMed MCP - FDA Structured Product Labels via NLM. | Remote · HTTPLive check: ✓ handshake |