Medicare Coverage
Server Details
MCP server for medicare-coverage
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 32.4% over 42 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-medicare-coverage
- GitHub Stars
- 0
- Server Listing
- mcp-medicare-coverage
TDQS
Scored across 58 tools
The tool set is a mix of two clearly different domains: a large family of ~30 medicare_* coverage/utilization tools plus a ~25-tool meta/research/memory/subscription layer (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, polymarket_*). Within the Pipeworx layer there are multiple near-duplicate routers (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) and overlapping polymarket tools (polymarket_edges vs polymarket_arbitrage vs polymarket_kalshi_spread) whose boundaries require long descriptions to separate. Within the medicare_* family many tools differ only by granularity (trend vs market vs exposure for DME, HCPCS, DRG, APC, post-acute), which is hard to disambiguate without careful reading.
The medicare_* tools follow a strong, predictable snake_case prefix pattern (medicare_ncd_search, medicare_ncd_detail, medicare_lcd_search, medicare_lcd_detail, etc.). The non-medicare tools are also snake_case, though the naming style is a bit mixed across families (ask_pipeworx_beta, ai_visibility_check, compare_entities) — still readable and consistent overall.
58 tools is far more than the apparent scope can justify. The server appears to bundle a full Medicare coverage/utilization domain (30+ tools) with an entire separate meta/research/prediction-market platform (25+ tools), plus memory (remember/recall/forget) and subscription management (subscribe/unsubscribe/list_subscriptions/recent_alerts) — a heavy surface that will overwhelm agents trying to pick a tool.
For the Medicare coverage domain specifically, the surface is reasonably rich (NCD/LCD/NCA search and detail, timelines, utilization, spend, enrollment, provider markets) with a plausible CRUD-like read surface. However, several clearly distinct domains are packed in (pipeworx routing, polymarket, memory, subscriptions, entity resolution), and none of those sub-domains is fully covered on its own — and the medicare_* tools are read-only, with no clear write/lifecycle operations. Coverage is broad but shallow across multiple domains.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
entity_profile3 fields changed- changed
Input schema / properties / type / descriptionPrevious value: -"Entity type. Only \"company\" supported today; person/place coming soon."New value: +"\"company\" or \"ticker\" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way. person/place coming soon." - changed
Input schema / properties / type / enumPrevious value: -[ - "company" -]New value: +[ + "company", + "ticker" +] - changed
Input schema / properties / value / descriptionPrevious value: -"Ticker (e.g., \"AAPL\") or zero-padded CIK (e.g., \"0000320193\"). Names not supported — use resolve_entity first if you only have a name."New value: +"Ticker (e.g., \"AAPL\"), zero-padded CIK (e.g., \"0000320193\"), or company name (e.g., \"Moderna\") — names resolve via SEC EDGAR company-name match."
1 tool update
- Changed
resolve_entity1 field changed- changed
Input schema / properties / value / descriptionPrevious value: -"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\")."New value: +"For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., \"ozempic\", \"metformin\"). Pass the ENTITY NAME ONLY — for a bond that is the ISSUER exactly as printed (\"NEW YORK ST DORM AUTH\"), never the question's full noun phrase (\"NEW YORK ST DORM AUTH revenue bonds\"): the FIGI lookup matches instrument names, so trailing security-class words match nothing."
Related MCP Connectors
MCP server for medicaid-intelligence
MCP server for US nursing facility search and ownership lookup (NursingHomeDatabase).
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for looking up and searching US healthcare providers in the CMS NPPES NPI Registry.MIT
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables querying Medicaid drug utilization, managed-care enrollment, and state enrollment data from CMS's public Medicaid Open Data API, with tools for trends, market analysis, and program mix without authentication.171 npmMIT
- FlicenseBqualityCmaintenanceMCP server for headless care coordination, providing tools for case-aware provider search powered by ai-carematch.4-
- FlicenseNot gradedqualityDmaintenanceThis MCP server enables medicine management, stock/refill estimation, doctor search and availability checks, and appointment management for senior care scenarios.-
Glama MCP Gateway
Add one secure layer between your agents and this server.