MCP.Market

Medicaid Intelligence MCP server

online · 96% uptime
by pipeworx-io·io.github.pipeworx-io/medicaid-intelligence·v0.2.1

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

B77/100grade B
What users say
No reviews yet
Be the first
Safety scan
B77/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Medicaid Intelligence yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Medicaid Intelligence tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Medicaid Intelligence compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Uptime
96%
of our recent checks; the typical remote server answers 100%
Response time
37 ms
faster than 94% of 30,031 servers

Release history: 6 versions in the registry since 2026-08-03, latest 2026-11-03, typically one every 5 days.

Install Medicaid Intelligence in Claude Code, Cursor or VS Code

claude mcp add --transport http medicaid-intelligence https://gateway.pipeworx.io/medicaid-intelligence/mcp
Add to Cursor

What the publisher says

From the Medicaid Intelligence repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/medicaid-intelligence

Medicaid drug utilization, managed-care enrollment and state enrollment operations from the CMS Medicaid Open Data API. Keyless.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

Auth

None. Every endpoint is public CMS infrastructure at data.medicaid.gov.

Reading these numbers correctly

This source is easy to misread, and most of the pack's design is about preventing that. Each response carries an interpretation field stating the caveat that applies to it.

programs paid pharmacies. It is neither manufacturer revenue nor net price — Medicaid rebates are substantial and are not in this data. Treating these figures as a manufacturer's Medicaid revenue overstates it, often by a lot.

  • Reimbursement is gross, before rebates. totalamountreimbursed is what state Medicaid

suppression_used flag). Those become null, never 0, and a channel that is entirely suppressed is reported as unavailable rather than as an absence of utilization. Tests guard this specifically.

  • Suppressed is not zero. CMS suppresses small cells (DS, *, --, or a

not meaningful for most questions, because a state's mix shifts over time.

  • Fee-for-service and managed care are separate measures and stay separate. Adding them is

under comprehensive MCO and MLTSS and behavioral health. medicaidmanagedcareprogrammix says so in its interpretation.

  • Managed-care program categories overlap and must not be summed. A beneficiary can appear

a particular insurer. They do not map cleanly onto a payer's book of business.

  • Enrollment counts are state-reported program enrollment, not covered lives attributable to

medicaidplanmarket returns a bounded sample plus the authoritative total row count, so a short list never implies a small market.

  • A zero in the plan file can be confidentiality suppression, not an empty plan.

Argument conventions

The underlying datasets disagree about how a state is written — the drug files use two-letter codes, the enrollment and managed-care files use full names. Both forms are accepted on every tool and converted internally. This matters: before that, asking the managed-care summary for "CA" matched nothing and returned a confident total: 0, which reads as "California has no managed care" rather than as a wrong argument.

ndc takes an exact 11-digit National Drug Code, hyphenated or not. A brand or ingredient name returns {found:false, reason:'ndcexpectedgotname'} with a hint pointing at openfdadrug_label or rxnorm to resolve it first.

Failure shapes

A recoverable caller mistake resolves to {found:false, reason, hint} naming what to do instead. An upstream failure or a genuine defect resolves to {error, hint}. The two are deliberately distinguishable, so a monitoring sweep can tell "CMS refused us" apart from "we returned garbage".

Data sources

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Medicaid Intelligence: common questions

Is Medicaid Intelligence MCP server safe?
Mostly: it is graded B (77/100). Read the Medicaid Intelligence safety report
How do I install Medicaid Intelligence?
It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Medicaid Intelligence need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Medicaid Intelligence maintained?
The last commit was 46 days ago (2026-09-18). The latest release is v0.2.1.
Is Medicaid Intelligence up?
96% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Medicaid Intelligence compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 96% (of our recent checks; the typical remote server answers 100%); response time 37 ms (faster than 94% of 30,031 servers). Full comparison.

More from pipeworx-io →