# Cms Open Payments (npm · @pipeworx/mcp-cms-open-payments)

CMS Open Payments, with annual dataset discovery through the official DKAN API.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-cms-open-payments/cms-open-payments-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-cms-open-payments/cms-open-payments-mcp)
- npm · `@pipeworx/mcp-cms-open-payments`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-cms-open-payments/pipeworx-mcp-cms-open-payments.md), [page](https://verifymcp.io/servers/pipeworx-io-cms-open-payments/pipeworx-mcp-cms-open-payments)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-cms-open-payments`
- 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-05.

- **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-cms-open-payments).
  - 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**: 55/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 1536 tokens (~139/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 31% of tool parameters carry a description.
  - Structured output schemas are declared (91% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Cms Open Payments MCP server?

Cms Open Payments runs locally as an npm package, launched with npx -y @pipeworx/mcp-cms-open-payments. 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-cms-open-payments -- npx -y @pipeworx/mcp-cms-open-payments
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-cms-open-payments -- npx -y @pipeworx/mcp-cms-open-payments
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-cms-open-payments --command npx --arg -y --arg @pipeworx/mcp-cms-open-payments
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 79, +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 78, +1)

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

### 2026-11-01 (score 77, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 62, −14)

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

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

First indexed and scored.

## MCP tools (11)

### `open_payments_top_companies` (~197 tokens)

Rank the drug and device manufacturers that paid US physicians and teaching hospitals the most in a program year — the "who spends the most on doctors" question. Returns each company with its total US dollars, payment count and how many distinct recipients it reached, ordered by spend. CMS publishes no aggregate and its live API cannot group over the 14-million-row payment table, so this reads a summary computed offline; the response states the program year and when the summary was refreshed. Payments are disclosures of transfers of value, not evidence of wrongdoing.

Input parameters:

- `company` (string): Optional: one company, to get its total rather than the ranking. Matched case-insensitively.
- `limit` (number): Companies to return, 1-200 (default 25).
- `program_year` (number): Program year, e.g. 2025. Defaults to the most recent year loaded — the response always says which.

### `open_payments_search` (~373 tokens)

THE source for pharma/device industry money to doctors — "payments from manufacturers to physicians", "which drug companies paid this doctor", "Sunshine Act data", "industry payments to hospitals". Search one CMS Open Payments program-year dataset using structured recipient, company, product, geography, payment-nature, and amount filters. CAPABILITY LIMIT, state it rather than guessing: this source can look up and filter but CANNOT rank ALL manufacturers by total spend ("which manufacturer paid the most" is not computable live — the 14M-row aggregation times out upstream); answer those by saying so and offering a named-company lookup (open_payments_company) instead. CMS publishes company-reported relationships; a payment does not imply wrongdoing or a conflict.

Input parameters:

- `company` (string): Case-insensitive company-name substring.
- `limit` (number): Results (1-100, default 25).
- `minimum_amount` (number): Minimum reported payment in USD.
- `nature` (string): Exact nature of payment.
- `offset` (number): Pagination offset (0-10000).
- `payment_type` (string): Default General.
- `product` (string): Case-insensitive associated-product substring across all five product fields.
- `recipient_first_name` (string): Exact recipient first name, to disambiguate a common surname (e.g. last_name "PATEL" + first_name "RIPAL").
- `recipient_last_name` (string): Exact recipient last name. CMS stores names uppercase; case is normalized for you. Pair with recipient_first_name — a common surname alone matches many practitioners.
- `recipient_npi` (string): Exact 10-digit NPI.
- `state` (string): Exact two-letter recipient state.
- `year` (number): Program year (2019-current published year; default latest).

Output parameters:

- `dataset` (object)
- `interpretation` (string)
- `payment_type` (string)
- `payments` (array)
- `program_year` (number)
- `returned` (number)
- `total_matches` (number)

### `open_payments_physician` (~149 tokens)

Find CMS Open Payments records for a physician/non-physician practitioner by exact NPI in one program year. Returns the authoritative total match count plus a bounded payment sample; reported relationships do not imply misconduct. If you have a name rather than an NPI, resolve it first against the NPPES registry (npi_individual in the clinicaltables pack), or use open_payments_search with recipient_last_name + recipient_first_name.

Input parameters:

- `limit` (number): Payment rows (1-100, default 50).
- `npi` (string, required): Exact 10-digit NPI.
- `payment_type` (string)
- `year` (number): Program year; default latest.

Output parameters:

- `dataset` (object)
- `interpretation` (string)
- `payment_type` (string)
- `payments` (array)
- `program_year` (number)
- `returned` (number)
- `total_matches` (number)

### `open_payments_company` (~87 tokens)

Search payments reported by a manufacturer or GPO in one CMS Open Payments program year. Company matching is a case-insensitive substring and may combine similarly named legal entities.

Input parameters:

- `company` (string, required)
- `limit` (number)
- `minimum_amount` (number)
- `offset` (number)
- `payment_type` (string)
- `year` (number)

Output parameters:

- `dataset` (object)
- `interpretation` (string)
- `payment_type` (string)
- `payments` (array)
- `program_year` (number)
- `returned` (number)
- `total_matches` (number)

### `open_payments_product` (~89 tokens)

Search general-payment records associated with a named drug, biologic, device, or medical supply across all five CMS product slots. Product association is reporting-entity supplied and does not prove the payment was exclusively for that product.

Input parameters:

- `company` (string)
- `limit` (number)
- `offset` (number)
- `product` (string, required)
- `year` (number)

Output parameters:

- `dataset` (object)
- `interpretation` (string)
- `payment_type` (string)
- `payments` (array)
- `program_year` (number)
- `returned` (number)
- `total_matches` (number)

### `open_payments_research` (~117 tokens)

Search CMS research-payment records by company, recipient NPI, study name, or state for one program year. Amounts may represent funding routed through an institution and should not automatically be attributed as personal compensation.

Input parameters:

- `company` (string)
- `limit` (number)
- `minimum_amount` (number)
- `offset` (number)
- `recipient_npi` (string)
- `state` (string)
- `study` (string): Case-insensitive study-name substring.
- `year` (number)

Output parameters:

- `dataset` (object)
- `interpretation` (string)
- `payment_type` (string)
- `payments` (array)
- `program_year` (number)
- `returned` (number)
- `total_matches` (number)

### `open_payments_recipient_history` (~99 tokens)

Build a cross-year CMS Open Payments history for an exact recipient NPI. Returns authoritative annual match counts plus bounded samples; sampled dollar totals are explicitly not full-dataset totals.

Input parameters:

- `from_year` (number)
- `npi` (string, required)
- `payment_type` (string)
- `sample_per_year` (number): Rows per year (1-100, default 25).
- `to_year` (number)

Output parameters:

- `interpretation` (string)
- `sampled_amount_usd` (number)
- `sampled_records` (number)
- `total_matches_across_years` (number)
- `years` (array)

### `open_payments_company_history` (~91 tokens)

Build a cross-year CMS Open Payments history for a company-name substring. Annual counts are authoritative for that query; dollar figures cover only the returned bounded sample and company aliases may split or combine legal entities.

Input parameters:

- `company` (string, required)
- `from_year` (number)
- `payment_type` (string)
- `sample_per_year` (number)
- `to_year` (number)

Output parameters:

- `interpretation` (string)
- `sampled_amount_usd` (number)
- `sampled_records` (number)
- `total_matches_across_years` (number)
- `years` (array)

### `open_payments_product_history` (~85 tokens)

Build a cross-year general-payment history for a reported product-name substring across CMS product slots. Product association is reporter-supplied; sample dollar amounts are not complete annual totals.

Input parameters:

- `company` (string)
- `from_year` (number)
- `product` (string, required)
- `sample_per_year` (number)
- `to_year` (number)

Output parameters:

- `interpretation` (string)
- `sampled_amount_usd` (number)
- `sampled_records` (number)
- `total_matches_across_years` (number)
- `years` (array)

### `open_payments_compare_companies` (~91 tokens)

Compare 2–5 company-name queries across CMS Open Payments program years using authoritative match counts and clearly labeled bounded samples. This does not compare complete spend unless every matching row fits in the sample.

Input parameters:

- `companies` (array, required)
- `from_year` (number)
- `payment_type` (string)
- `sample_per_year` (number)
- `to_year` (number)

Output parameters:

- `companies` (array)
- `interpretation` (string)

### `open_payments_nature_breakdown` (~101 tokens)

Break down the bounded payment sample for one recipient, company, or product across years by reported nature of payment. Counts and dollars in the breakdown are sample statistics; annual total_matches remains the authoritative query count.

Input parameters:

- `company` (string)
- `from_year` (number)
- `npi` (string)
- `product` (string)
- `sample_per_year` (number)
- `to_year` (number)

Output parameters:

- `interpretation` (string)
- `nature_breakdown` (array)
- `years` (array)

## Diagnostics

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

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 62
- 2026-10-30: 76
- 2026-10-29: 76

## Common questions

### What is the Cms Open Payments MCP server?

Cms Open Payments is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cms-open-payments. CMS Open Payments, with annual dataset discovery through the official DKAN API. This page covers its npm package (@pipeworx/mcp-cms-open-payments).

### Is the Cms Open Payments MCP server safe to use?

Cms Open Payments scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Cms Open Payments MCP server expose?

Cms Open Payments exposes 11 tools: open_payments_top_companies, open_payments_search, open_payments_physician, open_payments_company, open_payments_product, and 6 more. Their descriptions and schemas cost roughly 1,479 tokens of context every time the server is loaded.

### Is the Cms Open Payments MCP server still maintained?

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

Cms Open Payments 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 Cms Open Payments MCP server?

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