# Drug Prices (npm · @pipeworx/mcp-drug-prices)

US drug price benchmarks — what a pharmacy PAYS and what Medicare PAYS OUT.

- Trust score: 83/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`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-drug-prices/drug-prices-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-drug-prices/drug-prices-mcp)
- npm · `@pipeworx/mcp-drug-prices`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-drug-prices/pipeworx-mcp-drug-prices.md), [page](https://verifymcp.io/servers/pipeworx-io-drug-prices/pipeworx-mcp-drug-prices)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-drug-prices`
- 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-drug-prices).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1515 tokens (~252/item across 6 items; 6 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Drug Prices MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 83, +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 82, +1)

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

### 2026-11-02 (score 81, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 80, 0)

- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 80, +1)

- [functional regression] Security disclosure: fail → unverified

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

First indexed and scored.

## MCP tools (6)

### `nadac_price` (~367 tokens)

What a US retail pharmacy actually PAYS to acquire a drug — the National Average Drug Acquisition Cost (NADAC), surveyed and published weekly by CMS. Look up by drug name ("atorvastatin 20 mg", "Eliquis", "insulin glargine") or by NDC. NAME MATCHING IS LITERAL: NADAC lists brand products under their BRAND name and generics under the ingredient name, so "Eliquis" finds rows where "apixaban" finds none — if one returns nothing, try the other. Returns the most recent weekly price per NDC with its pricing unit (EA/ML/GM), brand-or-generic classification, and the week the price applies to. This is the ACQUISITION cost, not a retail price, not an insurance copay, and not what Medicare pays a clinic — for a drug given in a doctor's office or infusion centre see asp_payment_limit. Keyless.

Input parameters:

- `as_of` (string): Optional ISO date (YYYY-MM-DD). Returns the pricing week in effect on that date instead of the newest. Use for "what did this cost in March".
- `drug` (string): Drug name or fragment, e.g. "atorvastatin 20 mg", "apixaban", "albuterol". Matched against the NDC description. Give either this or `ndc`.
- `limit` (number): Max NDCs to return, 1–100 (default 20).
- `ndc` (string): National Drug Code. Any common format accepted — 11-digit "00093505610", dashed 5-4-2 "00093-5056-10", or 10-digit; it is normalised to the canonical 11-digit form.

### `nadac_history` (~137 tokens)

Weekly price history for one drug NDC — how the pharmacy acquisition cost (NADAC) moved over time. Use for "has the price of this generic gone up", shortage-driven price spikes, or generic erosion after a patent expiry. Returns one row per published week, oldest to newest, with the pricing unit and the percentage change across the window. Keyless.

Input parameters:

- `ndc` (string, required): National Drug Code in any common format (11-digit, dashed 5-4-2, or 10-digit).
- `weeks` (number): How many recent weekly observations to return, 1–260 (default 26).

### `asp_payment_limit` (~294 tokens)

What Medicare Part B PAYS for a drug administered by a provider — the quarterly ASP payment limit, set by statute at 106% of the manufacturer-reported Average Sales Price. Look up by HCPCS J-code ("J9271") or drug name ("pembrolizumab", "Keytruda"). This is the clinic/infusion benchmark: oncology drugs, biologics, injectables and vaccines. Returns the limit per its dosage unit, the quarter it is in force, AND the earlier quarter of ASP data it was derived from — those differ by two quarters and the gap matters. For retail pharmacy acquisition cost use nadac_price instead. Keyless.

Input parameters:

- `drug` (string): Drug name or fragment matched against the short description, e.g. "pembrolizumab", "rituximab". Give either this or `hcpcs`.
- `hcpcs` (string): HCPCS code, e.g. "J9271" (pembrolizumab), "J0178" (aflibercept), "90632".
- `limit` (number): Max codes to return when searching by name, 1–100 (default 20).
- `quarter` (string): Optional quarter as a date in it, or "YYYY-Qn" (e.g. "2026-Q1", "2026-01-01"). Defaults to the most recent quarter loaded.

### `drug_price_compare` (~178 tokens)

Put the two US drug price benchmarks side by side for one drug — what a pharmacy pays to acquire it (NADAC, weekly) against what Medicare Part B pays a provider for it (ASP limit, quarterly). Use to see the spread between acquisition cost and reimbursement, or to check whether a drug is a retail or a clinic-administered product at all. States the vintage of each number and warns when they are measured months apart, because the ASP limit in force is derived from ASP data two quarters earlier. Returns whichever benchmarks exist — many drugs legitimately have only one. Keyless.

Input parameters:

- `drug` (string, required): Drug name, e.g. "pembrolizumab", "atorvastatin", "rituximab".
- `ndc` (string): Optional NDC to pin the NADAC side to one product.

### `b340_covered_entities` (~278 tokens)

Find 340B drug pricing program covered entities registered with HRSA: hospitals, community health centers, Ryan White HIV clinics, family planning and STD grantees. Filter by state, entity type or name and get the 340B ID, registration start date, parent hospital, Medicare CCN, NPI numbers and how many contract pharmacies each one uses. Answers which providers can buy drugs at 340B ceiling prices in a given state, whether a named hospital participates, and when it joined.

Input parameters:

- `id340b` (string): Exact 340B ID, e.g. "DSH340075H".
- `include_terminated` (boolean): Include entities no longer participating. Default false — 29,950 of 94,363 records are terminated registrations.
- `limit` (number): Max rows, default 25, max 200.
- `name` (string): Match part of the entity or subsidiary name, e.g. "Cleveland Clinic".
- `state` (string): Two-letter state or territory code, or a full state name ("TX" or "Texas").
- `type` (string): Entity type. Plain words work ("hospital", "health center", "Ryan White", "critical access", "homeless"), as do HRSA codes ("DSH", "CAH", "CH").

### `b340_contract_pharmacies` (~206 tokens)

List the contract pharmacies a 340B covered entity dispenses through, or work backwards from a pharmacy chain to the covered entities it serves. Returns pharmacy name, city, state, contract begin date and termination date. Answers how large a hospital 340B pharmacy network is, which chains a health center contracts with, and how many 340B relationships a chain like Walgreens or CVS holds in a state.

Input parameters:

- `id340b` (string): The covered entity, e.g. "DSH340075H". Give this or `pharmacy`.
- `include_terminated` (boolean): Include contracts whose termination date has passed. Default false.
- `limit` (number): Max rows, default 25, max 200.
- `pharmacy` (string): Match part of a pharmacy name, e.g. "Walgreens". Give this or `id340b`.
- `state` (string): Restrict to pharmacies in this state ("TX" or "Texas").

## Diagnostics

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

## Score history

- 2026-11-06: 83
- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Drug Prices MCP server?

Drug Prices is an MCP server listed in the public MCP registry as io.github.pipeworx-io/drug-prices. US drug price benchmarks, what a pharmacy PAYS and what Medicare PAYS OUT. This page covers its npm package (@pipeworx/mcp-drug-prices).

### Is the Drug Prices MCP server safe to use?

Drug Prices scores 83 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 Drug Prices MCP server expose?

Drug Prices exposes 6 tools: nadac_price, nadac_history, asp_payment_limit, drug_price_compare, b340_covered_entities, b340_contract_pharmacies. Their descriptions and schemas cost roughly 1,460 tokens of context every time the server is loaded.

### Is the Drug Prices MCP server still maintained?

Drug Prices 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 Drug Prices MCP server under?

Drug Prices 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 Drug Prices MCP server?

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