# Healthdata (npm · @pipeworx/mcp-healthdata)

HealthData.gov MCP. Keyless.

- Trust score: 91/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 87/100, [markdown](https://verifymcp.io/servers/pipeworx-io-healthdata/healthdata-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-healthdata/healthdata-mcp)
- npm · `@pipeworx/mcp-healthdata`: 91/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-healthdata/pipeworx-mcp-healthdata.md), [page](https://verifymcp.io/servers/pipeworx-io-healthdata/pipeworx-mcp-healthdata)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-healthdata`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-healthdata).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add pipeworx-io-healthdata -- npx -y @pipeworx/mcp-healthdata
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-healthdata": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-healthdata"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-healthdata": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-healthdata"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-healthdata -- npx -y @pipeworx/mcp-healthdata
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-healthdata": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-healthdata"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-healthdata --command npx --arg -y --arg @pipeworx/mcp-healthdata
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-healthdata:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-healthdata"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-healthdata": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-healthdata"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-healthdata -t stdio -c npx -a -y @pipeworx/mcp-healthdata
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-healthdata": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-healthdata"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 91, +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.

### 2026-11-20 (score 90, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-19 (score 90, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-18 (score 90, +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.

### 2026-11-16 (score 89, +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.

### 2026-11-14 (score 88, +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.

### 2026-11-12 (score 87, +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.

### 2026-11-10 (score 86, +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.

## MCP tools (3)

### `search_datasets` (~160 tokens)

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.

Input parameters:

- `limit` (number): Max results, 1-50 (default 10).
- `offset` (number): Skip this many results, for paging (default 0).
- `query` (string, required): Search query, e.g. "vaccination rates", "hospital readmissions".

### `get_dataset` (~128 tokens)

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.

Input parameters:

- `id` (string, required): Socrata 4x4, e.g. "g62h-syeh".

### `get_rows` (~174 tokens)

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.

Input parameters:

- `id` (string, required): Socrata 4x4, e.g. "g62h-syeh".
- `limit` (number): Rows to return, 1-1000 (default 20).
- `offset` (number): Skip this many rows (default 0).
- `order` (string): SoQL ordering, e.g. "date DESC".
- `where` (string): SoQL filter, e.g. "state = 'CA'".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-healthdata/pipeworx-mcp-healthdata#diagnostics

## Score history

- 2026-11-22: 91
- 2026-11-21: 91
- 2026-11-20: 90
- 2026-11-19: 90
- 2026-11-18: 90
- 2026-11-17: 89
- 2026-11-16: 89
- 2026-11-15: 88
- 2026-11-14: 88
- 2026-11-13: 87
- 2026-11-12: 87
- 2026-11-11: 86
- 2026-11-10: 86
- 2026-11-09: 85
- 2026-11-08: 80
- 2026-11-07: 84
- 2026-11-06: 84
- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 80

## 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-healthdata
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-healthdata
- Repository: https://github.com/pipeworx-io/mcp-healthdata
- Website: https://pipeworx.io/packs/healthdata
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-healthdata/pipeworx-mcp-healthdata.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-healthdata/pipeworx-mcp-healthdata/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-healthdata/pipeworx-mcp-healthdata.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-healthdata/pipeworx-mcp-healthdata
