Home / MCP registry index / io.github.pipeworx-io/medicare-pricing

Medicare Pricing

io.github.pipeworx-io/medicare-pricing in the official MCP registry. Endpoint https://gateway.pipeworx.io/medicare-pricing/mcp. Source: github.com/pipeworx-io/mcp-medicare-pricing.

The registry describes it as: What does Medicare PAY — physician fee schedule, lab rates, and per-day unit limits.

We read its 54 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_physician_payment medicare_lab_rate medicare_lab_test_lookup medicare_dmepos_rate medicare_opps_rate medicare_code_units_limit check_code_pair explain_ncci_edit medicare_fqhc_pps_rate medicare_gpci_lookup medicare_fqhc_gaf medicare_pricing_coverage

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-pipeworx-io-medicare-pricing/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-pipeworx-io-medicare-pricing)

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.