Skip to main content
Glama

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

A3.6/5.0

Scored across 58 tools

Disambiguation2/5

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.

Naming Consistency4/5

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.

Tool Count2/5

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.

Completeness3/5

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. 1 tool update
    • Changedentity_profile3 fields changed
      • changedInput schema / properties / type / description
        Previous 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."
      • changedInput schema / properties / type / enum
        Previous value: -[
        -  "company"
        -]New value: +[
        +  "company",
        +  "ticker"
        +]
      • changedInput schema / properties / value / description
        Previous 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."
  2. 1 tool update
    • Changedresolve_entity1 field changed
      • changedInput schema / properties / value / description
        Previous 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

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.