# Meps (npm · @pipeworx/mcp-meps)

MEPS — what Americans actually take, and what for.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-meps`
- 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-06.

- **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-meps).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 621 tokens (~155/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Meps MCP server?

Meps runs locally as an npm package, launched with npx -y @pipeworx/mcp-meps. 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-meps -- npx -y @pipeworx/mcp-meps
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-06 (score 84, +1)

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

### 2026-11-04 (score 83, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 67, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (4)

### `meps_drugs_for_condition` (~214 tokens)

Which prescription drugs Americans actually take for a given medical condition, with a national estimate of how many people take each one. Covers the whole US population — every payer, every age, commercial and uninsured included, not just Medicare or Medicaid. Ask with a plain condition name like "depression", "high cholesterol", "type 2 diabetes" or "asthma". Returns drugs ranked by estimated people treated, each with the survey sample behind it.

Input parameters:

- `condition` (string, required): Condition in plain words ("depression", "high blood pressure"), or a CCSR category code like MBD002.
- `limit` (number): Max drugs, default 20, max 100.
- `min_sample` (number): Minimum survey respondents behind a row, default 60 — AHRQ's own reliability floor. Lower it to see less-common drugs, which come back marked reliable:false because AHRQ would not publish them.
- `year` (number): Survey year. Defaults to the most recent loaded.

### `meps_conditions_for_drug` (~146 tokens)

What a drug is actually being prescribed for in the US population, ranked by estimated people. Answers off-label and multi-use questions that a label or an approval database cannot: what gabapentin, metformin or amitriptyline are really used to treat in practice. Give a generic drug name.

Input parameters:

- `drug` (string, required): Generic drug name, e.g. "gabapentin", "metformin".
- `limit` (number): Max conditions, default 20, max 100.
- `min_sample` (number): Minimum survey respondents behind a row, default 60.
- `year` (number): Survey year. Defaults to the most recent loaded.

### `meps_drug_use` (~109 tokens)

National prescription volume and spending for one drug: how many Americans filled it, how many fills, total spend across all payers and how much patients paid out of pocket. Population-wide rather than a single programme, so it answers how widely used a medicine is in the US and what share of its cost falls on patients.

Input parameters:

- `drug` (string, required): Generic drug name, e.g. "atorvastatin".
- `year` (number): Survey year. Defaults to the most recent loaded.

### `meps_top_drugs` (~100 tokens)

The most-used prescription drugs in the United States, ranked by estimated number of people who filled them, with total and out-of-pocket spending. Answers what the most commonly taken medications in America are for a given year.

Input parameters:

- `limit` (number): Max drugs, default 25, max 100.
- `order_by` (string): Ranking measure, default people.
- `year` (number): Survey year. Defaults to the most recent loaded.

## Diagnostics

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

## Score history

- 2026-11-06: 84
- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 67
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Meps MCP server?

Meps is an MCP server listed in the public MCP registry as io.github.pipeworx-io/meps. MEPS, what Americans actually take, and what for. This page covers its npm package (@pipeworx/mcp-meps).

### Is the Meps MCP server safe to use?

Meps scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 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 Meps MCP server expose?

Meps exposes 4 tools: meps_drugs_for_condition, meps_conditions_for_drug, meps_drug_use, meps_top_drugs. Their descriptions and schemas cost roughly 569 tokens of context every time the server is loaded.

### Is the Meps MCP server still maintained?

Meps is still listed as active in the MCP registry. We last reached this channel on 6 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 Meps MCP server under?

Meps 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 Meps MCP server?

VerifyMCP ran 16 checks on Meps, 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-meps
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-meps
- Repository: https://github.com/pipeworx-io/mcp-meps
- Website: https://pipeworx.io/packs/meps
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-meps/pipeworx-mcp-meps.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-meps/pipeworx-mcp-meps/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-meps/pipeworx-mcp-meps.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-meps/pipeworx-mcp-meps