MCP.Market

Mn Drug Price Transparency MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/mn-drug-price-transparency·v0.2.1

Minnesota manufacturer drug price-growth and new-drug-launch disclosures — the Minnesota half of…

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 Mn Drug Price Transparency yet.

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

Mn Drug Price Transparency 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 Mn Drug Price Transparency 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
100%
of our recent checks; the typical remote server answers 100%
Response time
214 ms
faster than 61% of 30,031 servers

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

Install Mn Drug Price Transparency in Claude Code, Cursor or VS Code

claude mcp add --transport http mn-drug-price-transparency https://gateway.pipeworx.io/mn-drug-price-transparency/mcp
Add to Cursor

What the publisher says

From the Mn Drug Price Transparency repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/mn-drug-price-transparency

Minnesota manufacturer drug price-growth and new-drug-launch disclosures — the Minnesota half of the fleet #3245 state WAC-transparency survey. See mcps/ca-drug-price-transparency/README.md for the full per-state survey.

Part of Pipeworx — an MCP gateway connecting AI agents to 1847+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

disclosures of a reported WAC (list price) increase, filed under Minnesota's Prescription Drug Price Transparency program.

  • mnrxprice_growth(drug?, manufacturer?, ndc?, limit?) — manufacturer

disclosures of a new drug launched above Minnesota's reporting threshold.

  • mnrxnewdruglaunches(drug?, manufacturer?, limit?) — manufacturer

Both answer from a periodically-refreshed table (not a live query — Minnesota publishes no API) and every response carries dataasof.

Auth

Keyless.

Data sources

Transparency program (Minn. Stat. 62J.84) — two periodic snapshot files: drugs with a reported WAC price increase, and new drugs launched above the reporting threshold. Not a per-year archive like California's CTRx program (see mcps/ca-drug-price-transparency), and no query API — refreshed by scripts/ingest-mn-rx-transparency.mjs.

  • Minnesota Department of Health (MDH), Prescription Drug Price

Traps

MDH's export uses the literal text "NULL" as its missing-value sentinel (confirmed 2026-10-18 on Patent Expiration Date etc, each paired with a same-row ... Not Applicable Indicator = 1) — a real ingest trap, since "NULL" is a non-empty, truthy string in JS and would otherwise be stored as the four literal characters rather than null. The parser checks for it explicitly.

Some narrative free-text fields (e.g. Price Increase Factors) already carry mojibake in MDH's own source file — mis-decoded punctuation like doesn’t for "doesn't". This is MDH's export, not something this ingest introduces; it is preserved as-is rather than guessed at, because a wrong re-encoding guess is worse than a visibly broken apostrophe.

No stable natural key. The same NDC recurs across multiple price-growth reports over time with no report id, so both tables use a surrogate bigserial key and a full-snapshot replace rather than an upsert.

A same-day rerun used to duplicate every row (found 2026-10-19, promoting this pack out of mcps/incubator/): the delete-stale step ran AFTER insert and only removed rows STRICTLY OLDER than the current dataasof, so dispatching the refresh workflow twice before MDH republishes inserted a second full copy and deleted nothing. Fixed by deleting everything at or before the current dataas_of BEFORE inserting — see scripts/ingest-mn-rx-transparency.mjs's header.

MDH's CDN 403s a bare curl/fetch with no identifying User-Agent — the exact same URL with one set returns 200. Not an auth wall; checked in scripts/ingest-mn-rx-transparency.mjs's UA constant.

Refresh

.github/workflows/mn-rx-transparency-refresh.yml runs monthly and on workflow_dispatch: ingest, then install the pack's workspace deps, then smoke the pack against the freshly loaded table with real credentials (GitHub Actions secrets only — no agent machine holds the Supabase service key).

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "mn-drug-price-transparency": {
      "url": "https://gateway.pipeworx.io/mn-drug-price-transparency/mcp"
    }
  }
}

What this endpoint actually serves

Shortened. The full README is on GitHub.

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

Mn Drug Price Transparency: common questions

Is Mn Drug Price Transparency MCP server safe?
Mostly: it is graded B (77/100). Read the Mn Drug Price Transparency safety report
How do I install Mn Drug Price Transparency?
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 Mn Drug Price Transparency need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Mn Drug Price Transparency maintained?
The last commit was 15 days ago (2026-10-19). The latest release is v0.2.1.
Is Mn Drug Price Transparency up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Mn Drug Price Transparency compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 214 ms (faster than 61% of 30,031 servers). Full comparison.

More from pipeworx-io →