Meps
NPM · @PIPEWORX/MCP-MEPS · 2 COMPONENTS
MEPS — what Americans actually take, and what for.
Available components
Last scanned (3 hours ago)
Scores higher than 80% of npm servers
Category Health and Science
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-meps). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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 →
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.
- 6 Nov 26 +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.
- 4 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-meps@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-meps |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-meps/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655365172 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d39eb46fb732c4f51a1bac3c0bfe082702d8bf27c13bae0d03342f00ec7eec0e104d91ae7ff7ddf31e9226f28fbf1262dc987a2f44da85a60bff7230e |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
meps_conditions_for_drug ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| drug | string | yes | 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. |
No output schema declared.
No examples provided.
meps_drug_use ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| drug | string | yes | Generic drug name, e.g. "atorvastatin". |
| year | number | – | Survey year. Defaults to the most recent loaded. |
No output schema declared.
No examples provided.
meps_drugs_for_condition ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | yes | 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. |
No output schema declared.
No examples provided.
meps_top_drugs ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-meps
claude mcp add pipeworx-io-meps -- npx -y @pipeworx/mcp-meps
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.