Medicaid Intelligence
NPM · @PIPEWORX/MCP-MEDICAID-INTELLIGENCE · 2 COMPONENTS
Investor-oriented Medicaid drug utilization, managed-care, and enrollment signals.
Available components
Last scanned (12 hours ago)
Scores higher than 72% 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-medicaid-intelligence). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1336 tokens (~167/item across 8 items; 8 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 Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
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-medicaid-intelligence@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-medicaid-intelligence |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-medicaid-intelligence/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3655330900 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3055fac4dde4cc2af4ad14be6078e2db175461411d78b0d65c5a659b3a7274a41d05eb61473a6083432c831a7d0e229d9cf4e2c611b3b89d891ce300e |
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 →
medicaid_drug_state_market ~207
Which states spend the most on a drug — one year of Medicaid reimbursement broken down by state, keeping fee-for-service and managed care separate. Ask by NAME ("Ozempic") or by an exact 11-digit NDC. Suppressed rows remain unavailable and totals are gross pharmacy reimbursement before rebates.
| Name | Type | Req | Description |
|---|---|---|---|
| drug | string | – | Drug name as it appears on the package, e.g. "Ozempic" or "Humira" — matched against the Medicaid product list, aggregating every package size. A generic ingredient is expanded to its NDCs automatica… |
| ndc | string | – | Exact 11-digit National Drug Code, hyphenated or not, e.g. "00002-1433-80". Optional — give this OR drug. An NDC narrows to one package size. |
| year | number | – | Calendar year 2020-2026. Defaults to the most recent year with data. |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
| states | array | yes | – |
| total | number | yes | – |
No examples provided.
medicaid_drug_trend ~326
How much Medicaid spent on a drug, year by year — annual prescriptions, units and gross reimbursement from 2020 onward, split between fee-for-service and managed care. Ask by NAME ("Ozempic", "Humira"): the name is matched against the Medicaid product list and aggregated across every package size, so this answers "how much did Medicaid spend on X" directly. An exact 11-digit NDC narrows to one package instead. Reimbursement is GROSS, before the rebates Medicaid negotiates, so it is not manufacturer revenue or net cost to the programme. Suppressed values are never converted to zero.
| Name | Type | Req | Description |
|---|---|---|---|
| drug | string | – | Drug name as it appears on the package, e.g. "Ozempic" or "Humira" — matched against the Medicaid product list, aggregating every package size. A generic ingredient is expanded to its NDCs automatica… |
| from_year | number | – | First calendar year, 2020 or later. Defaults to 2024 — pass an earlier year for a longer history. |
| ndc | string | – | Exact 11-digit National Drug Code, hyphenated or not, e.g. "00002-1433-80". Optional — give this OR drug. An NDC narrows to one package size. |
| state | string | – | US state, as a two-letter code ("CA") or a full name ("California") — both are accepted. |
| to_year | number | – | Last calendar year, 2026 or earlier. |
| Name | Type | Req | Description |
|---|---|---|---|
| drug | string | – | – |
| interpretation | string | yes | – |
| matched_by | string | yes | ndc | product_name | ndc_expansion. |
| ndc | string | – | Present only when the call was matched on an exact NDC. |
| source | string | yes | – |
| state | string|null | – | – |
| years | array | yes | – |
No examples provided.
medicaid_drug_utilization ~275
Quarterly state-level Medicaid utilization rows for a drug — prescriptions, units and reimbursement per state and quarter, separated into fee-for-service and managed care. Ask by NAME ("Ozempic") or by an exact 11-digit NDC. Reimbursement is gross before Medicaid rebates and is not manufacturer revenue or net price.
| Name | Type | Req | Description |
|---|---|---|---|
| drug | string | – | Drug name as it appears on the package, e.g. "Ozempic" or "Humira" — matched against the Medicaid product list, aggregating every package size. A generic ingredient is expanded to its NDCs automatica… |
| limit | number | – | – |
| ndc | string | – | Exact 11-digit National Drug Code, hyphenated or not, e.g. "00002-1433-80". Optional — give this OR drug. An NDC narrows to one package size. |
| offset | number | – | – |
| state | string | – | US state, as a two-letter code ("CA") or a full name ("California") — both are accepted. |
| utilization_type | string | – | Restrict to fee-for-service or managed-care records; omit for both. |
| year | number | – | Calendar year 2020-2026. Defaults to the most recent year with data. |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| records | array | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
| total | number | yes | – |
No examples provided.
medicaid_enrollment_operations ~90
Show monthly Medicaid and CHIP enrollment and application-processing indicators for one state. Values are preliminary or updated state reports and may include footnotes or missing periods.
| Name | Type | Req | Description |
|---|---|---|---|
| from_month | string | – | YYYYMM. |
| state | string | yes | US state, as a two-letter code ("CA") or a full name ("California") — both are accepted. |
| to_month | string | – | YYYYMM. |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| months | array | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
| total | number | yes | – |
No examples provided.
medicaid_managed_care_program_mix ~100
Show state Medicaid enrollment by managed-care program type, including comprehensive MCO, PCCM, MLTSS, behavioral health, dental, transportation, and PACE. Program counts overlap and must not be summed.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | US state, as a two-letter code ("CA") or a full name ("California") — both are accepted. |
| year | number | – | Calendar year; omit for every year published. |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
| total | number | yes | – |
| years | array | yes | – |
No examples provided.
medicaid_managed_care_summary ~90
Show annual state Medicaid enrollment and enrollment in any or comprehensive managed care. Counts are state-reported program enrollment, not covered lives attributable to a particular insurer.
| Name | Type | Req | Description |
|---|---|---|---|
| from_year | number | – | – |
| state | string | – | US state, as a two-letter code ("CA") or a full name ("California"). Omit for national totals. |
| to_year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
| total | number | yes | – |
| years | array | yes | – |
No examples provided.
medicaid_monthly_managed_care ~107
Show monthly Medicaid/CHIP enrollment for one state and managed-care participation category. Data-quality flags and confidentiality suppression are preserved.
| Name | Type | Req | Description |
|---|---|---|---|
| from_month | string | – | YYYYMM. |
| participation | string | yes | Exact CMS category, e.g. "Comprehensive managed care". |
| state | string | yes | US state, as a two-letter code ("CA") or a full name ("California") — both are accepted. |
| to_month | string | – | YYYYMM. |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| months | array | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
| total | number | yes | – |
No examples provided.
medicaid_plan_market ~85
Return a bounded API-order sample of Medicaid managed-care plan/program rows by state and optional year, with the authoritative matching-row count. Zero may represent confidentiality suppression in this source.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| offset | number | – | – |
| parent_organization | string | – | – |
| state | string | yes | Full state name. |
| year | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| interpretation | string | yes | – |
| plans | array | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
| total | number | yes | – |
No examples provided.
How do I install the Medicaid Intelligence MCP server?
Medicaid Intelligence runs locally as an npm package, launched with npx -y @pipeworx/mcp-medicaid-intelligence. 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-medicaid-intelligence
claude mcp add pipeworx-io-medicaid-intelligence -- npx -y @pipeworx/mcp-medicaid-intelligence
What is the Medicaid Intelligence MCP server?
Medicaid Intelligence is an MCP server listed in the public MCP registry as io.github.pipeworx-io/medicaid-intelligence. Investor-oriented Medicaid drug utilization, managed-care, and enrollment signals. This page covers its npm package (@pipeworx/mcp-medicaid-intelligence).
Is the Medicaid Intelligence MCP server safe to use?
Medicaid Intelligence scores 82 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 Medicaid Intelligence MCP server expose?
Medicaid Intelligence exposes 8 tools: medicaid_drug_utilization, medicaid_drug_state_market, medicaid_drug_trend, medicaid_managed_care_summary, medicaid_managed_care_program_mix, and 3 more. Their descriptions and schemas cost roughly 1,280 tokens of context every time the server is loaded.
Is the Medicaid Intelligence MCP server still maintained?
Medicaid Intelligence 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 Medicaid Intelligence MCP server under?
Medicaid Intelligence declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.