Skip to content
MCP ThesaurusMCP Thesaurus

Healthdata

CommunityGood60/100Claim

streamable-httpupdated 2mo ago

HealthData.gov MCP — wraps HealthData.gov CKAN API (free, no auth)

SourceWebsite

What can you do with Healthdata?

mcp-healthdata

HealthData.gov MCP — wraps HealthData.gov CKAN API (free, no auth)

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Tool Description
search_datasets Search HealthData.gov for public health datasets by keyword (e.g., "COVID hospitalizations", "Medicare spending", "opioid prescriptions"). Returns dataset titles, descriptions, organizations, and resource links.
get_dataset Get full metadata for a HealthData.gov dataset by its package ID. Returns title, description, organization, resources (CSV/JSON download links), update frequency, and tags.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "healthdata": {
      "url": "https://gateway.pipeworx.io/healthdata/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/healthdata/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Healthdata data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT