Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Healthdata

NPM · @PIPEWORX/MCP-HEALTHDATA · 2 COMPONENTS

HealthData.gov MCP. Keyless.

+3 this week 91 Trust /100

Last scanned (5 hours ago)

Scores higher than 88% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-healthdata). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 20 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 514 tokens (~171/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 19 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Analysed npm/@pipeworx/mcp-healthdata@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-healthdata
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-healthdata/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637389431
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:0f9da087f90533d3c097c4ca1d3ddae25529efe90aa55451013c7a531a8da3cab1d9c0eac6c1906f8d8b9b2d4b87b6ad5ea52fb6937d3c5c18f027ffc

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~462 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_dataset ~128

Full metadata for one HealthData.gov dataset by its Socrata id (a 4x4 like "g62h-syeh", returned by search_datasets). Returns title, description, owning agency, licence, every column with its type, row count and the last data update. NOTE: HealthData.gov migrated off CKAN, so an old CKAN package id or slug will NOT resolve — search for the dataset again to get its 4x4.

NameTypeReqDescription
idstringyesSocrata 4x4, e.g. "g62h-syeh".

No output schema declared.

No examples provided.

get_rows ~174

Read actual rows from a HealthData.gov dataset by its Socrata 4x4 id. Optional SoQL `where` (e.g. "state = 'CA'") and `order` (e.g. "date DESC"). Use get_dataset first to see the column names. This returns the DATA, not a download link.

NameTypeReqDescription
idstringyesSocrata 4x4, e.g. "g62h-syeh".
limitnumber–Rows to return, 1-1000 (default 20).
offsetnumber–Skip this many rows (default 0).
orderstring–SoQL ordering, e.g. "date DESC".
wherestring–SoQL filter, e.g. "state = 'CA'".

No output schema declared.

No examples provided.

search_datasets ~160

Search HealthData.gov for public-health datasets by keyword (e.g. "COVID hospitalizations", "Medicare spending", "opioid prescriptions"). Returns each dataset's Socrata id (a 4x4 like "g62h-syeh"), title, description, owning agency, tags, when the data was last updated, and its page-view count. Pass the id to get_dataset for full metadata or to get_rows to read the actual rows.

NameTypeReqDescription
limitnumber–Max results, 1-50 (default 10).
offsetnumber–Skip this many results, for paging (default 0).
querystringyesSearch query, e.g. "vaccination rates", "hospital readmissions".

No output schema declared.

No examples provided.

Install

How do I install the Healthdata MCP server?

Healthdata runs locally as an npm package, launched with npx -y @pipeworx/mcp-healthdata. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-healthdata

# add to Claude Code
claude mcp add pipeworx-io-healthdata -- npx -y @pipeworx/mcp-healthdata
Common questions

What is the Healthdata MCP server?

Healthdata is an MCP server listed in the public MCP registry as io.github.pipeworx-io/healthdata. HealthData.gov MCP. Keyless. This page covers its npm package (@pipeworx/mcp-healthdata).

Is the Healthdata MCP server safe to use?

Healthdata scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Healthdata MCP server expose?

Healthdata exposes 3 tools: search_datasets, get_dataset, get_rows. Their descriptions and schemas cost roughly 462 tokens of context every time the server is loaded.

Is the Healthdata MCP server still maintained?

Healthdata is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Healthdata MCP server under?

Healthdata declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Healthdata MCP server?

VerifyMCP ran 16 checks on Healthdata, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.