Healthdata
Server Details
HealthData.gov MCP. Keyless.
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
- 31.0% over 49 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-healthdata
- GitHub Stars
- 0
- Server Listing
- mcp-healthdata
TDQS
Scored across 33 tools
Several tools have overlapping broad-research purposes: ask_pipeworx, ask_pipeworx_beta (currently identical to stable), ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions, entity_profile, compare_entities, recent_changes, and bet_research all perform fan-out lookup or discovery. The Polymarket cluster also has partially overlapping arbitrage/edge/risk tools. Descriptions help, but an agent can still easily misselect among them.
All tool names use snake_case and are generally readable, with domain prefixes for related groups (ask_pipeworx*, polymarket_*, pipeworx_*). The pattern is not strictly verb_noun throughout (e.g., entity_profile, recent_changes, ai_visibility_check), but it is consistent enough to be predictable.
33 tools is well above the typical 3–15 well-scoped range and includes duplicative variants such as ask_pipeworx_beta alongside ask_pipeworx. While the server spans multiple domains, the count feels heavy and could be consolidated without losing core capability.
The surface covers memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/list/recent_alerts), entity resolution, research, health datasets, Polymarket analytics, and dependency checks. Minor gaps exist, such as no direct generic Pipeworx tool executor or HealthData resource download, but agents can generally work around them.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +] - changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
Related MCP Connectors
US federal enforcement actions MCP. Keyless.
UK Health Security Agency (UKHSA) data dashboard MCP — keyless.
CMS Open Data MCP — US Centers for Medicare & Medicaid Services.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenance26 US federal data domains as 23 MCP tools. Ed25519 signed responses. Free, no API key.104 npm1MIT
- AlicenseBqualityCmaintenanceMCP server for Kenya health system — NHIF/SHA coverage, facility finder, community health workers, maternal health guidance, essential medicines.629 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that lets an LLM explore, query, aggregate, and benchmark the ~234 datasets in the CMS Provider Data Catalog — hospitals, dialysis facilities, nursing homes, home health, hospice, physicians, and more — in plain language.AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceOfficial Medplum MCP server for healthcare automation2,983 npm2,716Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.