Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ca Drug Price Transparency

NPM · @PIPEWORX/MCP-CA-DRUG-PRICE-TRANSPARENCY · 2 COMPONENTS

California manufacturer drug list-price (WAC) disclosures — HCAI Cost Transparency Rx (CTRx)…

+3 this week 82 Trust /100

Last scanned (11 hours ago)

Scores higher than 72% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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-ca-drug-price-transparency). 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 Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 820 tokens (~273/item across 3 items; 3 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Changelog

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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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
    • Security disclosure: unverified → fail ▼ functional
  • 31 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: fail → unverified ▼ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 79

    First indexed and scored.

Diagnostics

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-ca-drug-price-transparency@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-ca-drug-price-transparency
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-ca-drug-price-transparency/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606636874
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5c6522c5b190cb7438a2f3f13fd3eed0e6f0b8d901278c5008e68976ff75b2e252d6b237ae68e3c04b43eb36d2906484e024a80e1443a589b3efc1217

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~760 tokens

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 →

Tool Tokens
ca_rx_new_drug_launches ~242

California manufacturer disclosures of a NEW prescription drug launched with a Wholesale Acquisition Cost (WAC — published list price) exceeding the Medicare Part D specialty-drug cost threshold — California's "launch price" transparency requirement, filed with HCAI's Cost Transparency Rx (CTRx) program (same law as ca_rx_wac_increases, different trigger: a NEW drug's starting price rather than an existing drug's price increase). Search by drug name/fragment or manufacturer, optionally pinned to one report year (2019-present). Returns the launch WAC, estimated patient population, and breakthrough-therapy/priority-review FDA designations when disclosed. California-only. Keyless.

NameTypeReqDescription
drugstring–Drug name or fragment, e.g. "Vraylar", "Opdualag".
limitnumber–Max records to return, 1-100 (default 25).
manufacturerstring–Manufacturer name or fragment, e.g. "AbbVie", "Bristol Myers Squibb".
yearstring–Report year, "2019".."2026". Omit to search every available year.

No output schema declared.

No examples provided.

ca_rx_wac_five_year_history ~183

The 5-year WAC increase history California requires manufacturers to disclose alongside each WAC Increase Report — every prior increase for that NDC over the preceding 5 calendar years, with its date and amount. Use this to see a drug's full price trajectory rather than just its latest jump (ca_rx_wac_increases). Lookup is by NDC (get one from ca_rx_wac_increases first if you only have a drug name). Part of HCAI's CTRx program. California-only. Keyless.

NameTypeReqDescription
limitnumber–Max history rows to return, 1-200 (default 50).
ndcstringyesNational Drug Code, any common format.
yearstring–Report year to pin to, "2019".."2026". Omit to search every available year.

No output schema declared.

No examples provided.

ca_rx_wac_increases ~335

California manufacturer disclosures of a prescription drug's Wholesale Acquisition Cost (WAC — the published list price before rebates/discounts) going UP. Required by California law (SB 17/AB 265) whenever a drug's WAC exceeds $40 for a course of therapy AND the increase exceeds the statutory cumulative threshold; filed with HCAI's Cost Transparency Rx (CTRx) program. Search by drug name/fragment, manufacturer, or NDC, optionally pinned to one report year (2019-present; omit to search every year). Returns each increase's amount, the WAC after the increase, and whether the record comes from the still-open current year or a closed annual archive. This is the LIST price a manufacturer sets, not what any payer or pharmacy actually pays — for that, see the drug-prices pack's nadac_price/asp_payment_limit tools. California-only: see the pack README for which other states publish this and in what form. Keyless.

NameTypeReqDescription
drugstring–Drug name or fragment, e.g. "Humira", "insulin glargine", matched against the drug product description.
limitnumber–Max records to return, 1-100 (default 25).
manufacturerstring–Manufacturer name or fragment, e.g. "AbbVie", "Novo Nordisk".
ndcstring–National Drug Code, any common format.
yearstring–Report year, "2019".."2026". Omit to search every available year (recommended for a single drug/manufacturer/NDC lookup).

No output schema declared.

No examples provided.

Install

How do I install the Ca Drug Price Transparency MCP server?

Ca Drug Price Transparency runs locally as an npm package, launched with npx -y @pipeworx/mcp-ca-drug-price-transparency. 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-ca-drug-price-transparency

# add to Claude Code
claude mcp add pipeworx-io-ca-drug-price-transparency -- npx -y @pipeworx/mcp-ca-drug-price-transparency
Common questions

What is the Ca Drug Price Transparency MCP server?

Ca Drug Price Transparency is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ca-drug-price-transparency. California manufacturer drug list-price (WAC) disclosures, HCAI Cost Transparency Rx (CTRx)… This page covers its npm package (@pipeworx/mcp-ca-drug-price-transparency).

Is the Ca Drug Price Transparency MCP server safe to use?

Ca Drug Price Transparency 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 Ca Drug Price Transparency MCP server expose?

Ca Drug Price Transparency exposes 3 tools: ca_rx_wac_increases, ca_rx_wac_five_year_history, ca_rx_new_drug_launches. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.

Is the Ca Drug Price Transparency MCP server still maintained?

Ca Drug Price Transparency 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 Ca Drug Price Transparency MCP server under?

Ca Drug Price Transparency declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.