Cms Open Payments
NPM · @PIPEWORX/MCP-CMS-OPEN-PAYMENTS · 2 COMPONENTS
CMS Open Payments, with annual dataset discovery through the official DKAN API.
Available components
Last scanned (54 minutes ago)
Scores higher than 61% of npm servers
Category Finance and Payments
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-cms-open-payments). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- AI-judged instruction clarity (fair).Partial
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 31% of tool parameters carry a description.Partial
- Structured output schemas are declared (91% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 76
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-cms-open-payments@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-cms-open-payments |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-cms-open-payments/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612125222 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bfd6e6a458ea28b9868a38d3f1b9a156893a82822b52a47475225af51d0e9418c2a97a96d5347791a879657f778bd4db9fd5ba419a7cd068025dd9c6a |
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 →
open_payments_company ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| limit | number | – | – |
| minimum_amount | number | – | – |
| offset | number | – | – |
| payment_type | string | – | – |
| year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | object | yes | – |
| interpretation | string | yes | – |
| payment_type | string | yes | – |
| payments | array | yes | – |
| program_year | number | yes | – |
| returned | number | yes | – |
| total_matches | number | yes | – |
No examples provided.
open_payments_company_history ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| from_year | number | – | – |
| payment_type | string | – | – |
| sample_per_year | number | – | – |
| to_year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| sampled_amount_usd | number | yes | – |
| sampled_records | number | yes | – |
| total_matches_across_years | number | yes | – |
| years | array | yes | – |
No examples provided.
open_payments_compare_companies ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| from_year | number | – | – |
| payment_type | string | – | – |
| sample_per_year | number | – | – |
| to_year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| interpretation | string | yes | – |
No examples provided.
open_payments_nature_breakdown ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| from_year | number | – | – |
| npi | string | – | – |
| product | string | – | – |
| sample_per_year | number | – | – |
| to_year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| nature_breakdown | array | yes | – |
| years | array | yes | – |
No examples provided.
open_payments_physician ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Payment rows (1-100, default 50). |
| npi | string | yes | Exact 10-digit NPI. |
| payment_type | string | – | – |
| year | number | – | Program year; default latest. |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | object | yes | – |
| interpretation | string | yes | – |
| payment_type | string | yes | – |
| payments | array | yes | – |
| program_year | number | yes | – |
| returned | number | yes | – |
| total_matches | number | yes | – |
No examples provided.
open_payments_product ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| limit | number | – | – |
| offset | number | – | – |
| product | string | yes | – |
| year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | object | yes | – |
| interpretation | string | yes | – |
| payment_type | string | yes | – |
| payments | array | yes | – |
| program_year | number | yes | – |
| returned | number | yes | – |
| total_matches | number | yes | – |
No examples provided.
open_payments_product_history ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| from_year | number | – | – |
| product | string | yes | – |
| sample_per_year | number | – | – |
| to_year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| sampled_amount_usd | number | yes | – |
| sampled_records | number | yes | – |
| total_matches_across_years | number | yes | – |
| years | array | yes | – |
No examples provided.
open_payments_recipient_history ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from_year | number | – | – |
| npi | string | yes | – |
| payment_type | string | – | – |
| sample_per_year | number | – | Rows per year (1-100, default 25). |
| to_year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| sampled_amount_usd | number | yes | – |
| sampled_records | number | yes | – |
| total_matches_across_years | number | yes | – |
| years | array | yes | – |
No examples provided.
open_payments_research ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| limit | number | – | – |
| minimum_amount | number | – | – |
| offset | number | – | – |
| recipient_npi | string | – | – |
| state | string | – | – |
| study | string | – | Case-insensitive study-name substring. |
| year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | object | yes | – |
| interpretation | string | yes | – |
| payment_type | string | yes | – |
| payments | array | yes | – |
| program_year | number | yes | – |
| returned | number | yes | – |
| total_matches | number | yes | – |
No examples provided.
open_payments_search ~373
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | object | yes | – |
| interpretation | string | yes | – |
| payment_type | string | yes | – |
| payments | array | yes | – |
| program_year | number | yes | – |
| returned | number | yes | – |
| total_matches | number | yes | – |
No examples provided.
open_payments_top_companies ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-cms-open-payments
claude mcp add pipeworx-io-cms-open-payments -- npx -y @pipeworx/mcp-cms-open-payments
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.