# Medicaid Intelligence (npm · @pipeworx/mcp-medicaid-intelligence)

Investor-oriented Medicaid drug utilization, managed-care, and enrollment signals.

- Trust score: 82/100 (high trust)
- 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-medicaid-intelligence/medicaid-intelligence-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-medicaid-intelligence/medicaid-intelligence-mcp)
- npm · `@pipeworx/mcp-medicaid-intelligence`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-medicaid-intelligence/pipeworx-mcp-medicaid-intelligence.md), [page](https://verifymcp.io/servers/pipeworx-io-medicaid-intelligence/pipeworx-mcp-medicaid-intelligence)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-medicaid-intelligence`
- 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-medicaid-intelligence).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - 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.
  - 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**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
  - Structured output schemas are declared (100% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 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.

### Claude

```bash
claude mcp add pipeworx-io-medicaid-intelligence -- npx -y @pipeworx/mcp-medicaid-intelligence
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-medicaid-intelligence -- npx -y @pipeworx/mcp-medicaid-intelligence
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-medicaid-intelligence --command npx --arg -y --arg @pipeworx/mcp-medicaid-intelligence
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 82, +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.

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −14)

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

### 2026-10-31 (score 80, +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.

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

First indexed and scored.

## MCP tools (8)

### `medicaid_drug_utilization` (~275 tokens)

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.

Input parameters:

- `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.

Output parameters:

- `interpretation` (string)
- `records` (array)
- `returned` (number)
- `source` (string)
- `total` (number)

### `medicaid_drug_state_market` (~207 tokens)

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.

Input parameters:

- `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.

Output parameters:

- `interpretation` (string)
- `returned` (number)
- `source` (string)
- `states` (array)
- `total` (number)

### `medicaid_drug_trend` (~326 tokens)

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.

Input parameters:

- `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.

Output parameters:

- `drug` (string)
- `interpretation` (string)
- `matched_by` (string): ndc | product_name | ndc_expansion.
- `ndc` (string): Present only when the call was matched on an exact NDC.
- `source` (string)
- `state` (string|null)
- `years` (array)

### `medicaid_managed_care_summary` (~90 tokens)

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.

Input parameters:

- `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)

Output parameters:

- `interpretation` (string)
- `returned` (number)
- `source` (string)
- `total` (number)
- `years` (array)

### `medicaid_managed_care_program_mix` (~100 tokens)

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.

Input parameters:

- `state` (string, required): 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.

Output parameters:

- `interpretation` (string)
- `returned` (number)
- `source` (string)
- `total` (number)
- `years` (array)

### `medicaid_plan_market` (~85 tokens)

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.

Input parameters:

- `limit` (number)
- `offset` (number)
- `parent_organization` (string)
- `state` (string, required): Full state name.
- `year` (number)

Output parameters:

- `interpretation` (string)
- `plans` (array)
- `returned` (number)
- `source` (string)
- `total` (number)

### `medicaid_monthly_managed_care` (~107 tokens)

Show monthly Medicaid/CHIP enrollment for one state and managed-care participation category. Data-quality flags and confidentiality suppression are preserved.

Input parameters:

- `from_month` (string): YYYYMM.
- `participation` (string, required): Exact CMS category, e.g. "Comprehensive managed care".
- `state` (string, required): US state, as a two-letter code ("CA") or a full name ("California") — both are accepted.
- `to_month` (string): YYYYMM.

Output parameters:

- `interpretation` (string)
- `months` (array)
- `returned` (number)
- `source` (string)
- `total` (number)

### `medicaid_enrollment_operations` (~90 tokens)

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.

Input parameters:

- `from_month` (string): YYYYMM.
- `state` (string, required): US state, as a two-letter code ("CA") or a full name ("California") — both are accepted.
- `to_month` (string): YYYYMM.

Output parameters:

- `interpretation` (string)
- `months` (array)
- `returned` (number)
- `source` (string)
- `total` (number)

## Diagnostics

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

## Score history

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

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-medicaid-intelligence
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-medicaid-intelligence
- Repository: https://github.com/pipeworx-io/mcp-medicaid-intelligence
- Website: https://pipeworx.io/packs/medicaid-intelligence
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-medicaid-intelligence/pipeworx-mcp-medicaid-intelligence.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-medicaid-intelligence/pipeworx-mcp-medicaid-intelligence.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-medicaid-intelligence/pipeworx-mcp-medicaid-intelligence