Home / MCP registry index / io.github.pipeworx-io/medicare-coverage
Medicare Coverage
io.github.pipeworx-io/medicare-coverage in the official MCP registry.
Endpoint https://gateway.pipeworx.io/medicare-coverage/mcp. Source: github.com/pipeworx-io/mcp-medicare-coverage.
The registry describes it as: MCP server for medicare-coverage
We read its 69 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ask_pipeworx ask_pipeworx_beta ask_pipeworx_grounded search_within deep_research discover_tools resolve_entity compare_entities subscribe unsubscribe list_subscriptions recent_alerts entity_profile recent_changes validate_claim company_facts company_register_search scan_dependency bet_research polymarket_arbitrage polymarket_edges polymarket_kalshi_spread polymarket_fill_risk polymarket_edge_tracker kalshi_weather_edge resolution_audit resolution_diff release_calendar_markets prediction_calibration archive_evidence archive_compare research_row classify_row pipeworx_trending suggest_questions generate_llms_txt ai_visibility_check scan_competitor_ai_presence pipeworx_feedback remember recall forget medicare_ncd_search medicare_ncd_detail medicare_lcd_search medicare_lcd_detail medicare_nca_search medicare_nca_detail medicare_recent_coverage_changes medicare_coverage_states medicare_article_code_profile medicare_local_coverage_variation medicare_coverage_timeline medicare_hcpcs_utilization_trend medicare_hcpcs_geography medicare_provider_exposure medicare_product_market_profile medicare_part_d_top_drugs medicare_part_d_drug_spending medicare_part_d_prescriber_exposure and 9 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-pipeworx-io-medicare-coverage)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.