Medplum MCP
Securely access and manage FHIR healthcare data stored in Medplum.
California manufacturer drug list-price (WAC) disclosures — HCAI Cost Transparency Rx (CTRx)…
一覧は利用スコア(100 点満点)で並びます。内訳は次のとおり
| 人気 | 0/80 | GitHub スターか週間ダウンロード数。大きい方を 60、小さい方を 20 で数えます |
|---|---|---|
| 新しさ | 12/12 | 30 日以内のリリースかコード更新で満点 |
| 応答中 | 8/8 | 前回の確認でクラウドのエンドポイントが応答 |
| 利用スコア | 20/100 |
品質: 基本チェック 5/5 項目に合格(表示のみ、並び順には不使用) · 勢い: データなし (「急上昇」タブでのみ使用)
使っているAIアプリを選んで、設定をコピーしてください。
ひとことで AI にインストールしてもらう
Ca Drug Price Transparency をインストールして。https://mcp.popnx.com/i/pipeworx-io-ca-drug-price-transparency.md に従い、コマンドを見せて、私が OK するまで実行しないで。パソコンで作業できる AI(Claude Code や Cursor など)に貼り付けます。手順を読み、コマンドを見せて、あなたの OK を待ちます。キー不要・登録不要。 · AI が読む全文を見る
チェック 5/5 合格 · 質問内容は提供元のサーバー(gateway.pipeworx.io)を通ります · ✓ コマンド確認済み 2026年11月14日
まず:どの AI を使っていますか?
使っているアプリを選ぶと、下に手順が表示されます。
Claude につなげます · 約 2 分
キー不要、インストール不要 · claude.ai かデスクトップアプリで一度設定すれば、チャットで使えます · 無料アカウントは 1 つまで · Team/Enterprise はオーナー(Owner)が追加
CustomizeConnectors
ここからコピーして Claude の同じ名前の欄に貼り付け、Continue を押します
Ca Drug Price Transparencyhttps://gateway.pipeworx.io/ca-drug-price-transparency/mcpClaude が検出したサインイン設定の画面で Continue を押す · Authentication は作者の説明どおり(Sign in now・Sign in when needed・No sign in)を選び Add を押します
+ConnectorsCa Drug Price Transparency
Ca Drug Price Transparency を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が Ca Drug Price Transparency を使っていると言うか、回答に Ca Drug Price Transparency のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT との接続はプランしだい
フル MCP:Web 版 ChatGPT の Business・Enterprise・Edu · Pro:読み取り/取得の権限で接続、データを変えるツールは使えないことがあります · Plus:公式ドキュメントで未確認。プラグイン画面にカスタム MCP を追加する項目があれば試せます · Web のみ
Plugins+Add custom MCP server
名前を入れ、Connection にアドレスを貼り付け、注意事項にチェックして Create as a plugin を押します
Ca Drug Price Transparencyhttps://gateway.pipeworx.io/ca-drug-price-transparency/mcp新しいチャットを開き、入力前にプラグインの一覧から Ca Drug Price Transparency を選びます
Ca Drug Price Transparency を使って、私に何ができるか教えて、1 つやってみせて✓ ChatGPT が Ca Drug Price Transparency を使っていると言うか、回答に Ca Drug Price Transparency のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に OpenAI のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Claude Code につなげます · 約 2 分
キー不要、インストール不要
Mac:Command+スペースで Terminal と入力 · Windows:PowerShell を開く
claude mcp add --transport http --scope user ca-drug-price-transparency https://gateway.pipeworx.io/ca-drug-price-transparency/mcpCa Drug Price Transparency が一覧にあり、接続済みと表示されれば OK です
Ca Drug Price Transparency を使って、私に何ができるか教えて、1 つやってみせて✓ Claude Code が Ca Drug Price Transparency を使っていると言うか、回答に Ca Drug Price Transparency のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Cursor につなげます · 約 2 分
キー不要、インストール不要
Ca Drug Price Transparency を使って、私に何ができるか教えて、1 つやってみせて✓ Cursor が Ca Drug Price Transparency を使っていると言うか、回答に Ca Drug Price Transparency のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Cursor のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
VS Code につなげます · 約 2 分
キー不要、インストール不要
Ca Drug Price Transparency を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が Ca Drug Price Transparency を使っていると言うか、回答に Ca Drug Price Transparency のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください
Web 経由でつなぐアプリ用のアドレス
https://gateway.pipeworx.io/ca-drug-price-transparency/mcpJSON 設定は下の「開発者向け」にあります
Claude Code
claude mcp add --transport http --scope user ca-drug-price-transparency https://gateway.pipeworx.io/ca-drug-price-transparency/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ca-drug-price-transparency": {
"url": "https://gateway.pipeworx.io/ca-drug-price-transparency/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"ca-drug-price-transparency": {
"type": "http",
"url": "https://gateway.pipeworx.io/ca-drug-price-transparency/mcp"
}
}
}Claude Code
claude mcp add --scope user ca-drug-price-transparency -- npx -y @pipeworx/mcp-ca-drug-price-transparencyClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"ca-drug-price-transparency": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ca-drug-price-transparency"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"ca-drug-price-transparency": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ca-drug-price-transparency"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"ca-drug-price-transparency": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ca-drug-price-transparency"
]
}
}
}PIPEWORX_API_KEY 秘密 env説明は自動翻訳です。変数名は原文のままです。迷ったら原文を確認してください。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
npm: @pipeworx/mcp-ca-drug-price-transparencyこのサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。2026年11月10日に確認。
インターネット経由でつなげるアプリ
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
パソコン上で動かせるアプリ
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
ツールの名前と説明は、サーバーが2026年11月17日に返したそのままの内容です。書いたのは作者で、私たちではありません。プレーンテキストとして表示しています。
ask_pipeworxPREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring au
ask_pipeworx_betaBeta version of ask_pipeworx: identical universal router (same 7,551 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so
ask_pipeworx_groundedHallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,551 across 2011 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati
search_withinSemantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into th
deep_researchACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 2011 STRUCTURED data sources (SEC filings,
discover_toolsFind tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real est
resolve_entity"What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools re
compare_entities"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing
subscribeCreate a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = o
unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
list_subscriptionsList the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
recent_alertsPull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp).
entity_profile"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over cha
recent_changes"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings s
validate_claim"Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is f
company_factsTYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the pe
company_register_searchSearch the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CRO number, a CNPJ, a US state entity n
scan_dependencyComposite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular
bet_researchResearch a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it sett
polymarket_arbitrageFind arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `ev
polymarket_edgesScan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segme
polymarket_kalshi_spreadCross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says s
polymarket_fill_riskRealizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the di
polymarket_edge_trackerEdge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: d
kalshi_weather_edgePrices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob
resolution_auditExtract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. P
resolution_diffField-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equi
release_calendar_marketsJOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are c
prediction_calibrationREALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it
updown_venue_compareThe same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as
updown_divergence_rateHow often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair:
archive_evidenceWhat did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy
archive_compareWhat changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and b
research_rowClaygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code in
classify_rowCheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, e
pipeworx_trendingWhat other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice
suggest_questionsWhat can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed e
generate_llms_txtGenerate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at si
ai_visibility_checkProbe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns pe
scan_competitor_ai_presenceCompare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our co
pipeworx_feedbackTell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipewor
rememberSave data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-v
recallRetrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous
forgetDelete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
ca_rx_wac_increasesCalifornia 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
ca_rx_wac_five_year_historyThe 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
ca_rx_new_drug_launchesCalifornia 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 Transp
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月20日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント pipeworx-io で確認済みです
コードの最終更新:11 日前
MITを使用
192ミリ秒で応答(HTTP 200)
サインイン不要
47件のツールの説明を読み、AIへの隠れた指示は見つかりませんでした
OSV.dev に @pipeworx/mcp-ca-drug-price-transparency@0.2.1 の登録はありません
このバージョンのパッケージ本体のみ確認。すべての依存関係ではありません · 確認日 2026年11月15日
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/servers/pipeworx-io-ca-drug-price-transparency)質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。
まだレビューはありません
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック5項目のうち5項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
どちらでも使えます。パソコンにインストールしても、クラウド版につないでもかまいません。
GitHubリポジトリの最終更新は11 日前、最新バージョン(0.2.1)がレジストリに届いたのは20 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:Medplum MCP, Mirobody, Codescene MCP Server, Marrow, WHOOP — MissingMCP
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Securely access and manage FHIR healthcare data stored in Medplum.
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
An MCP server that provides CodeScene Code Health analysis tools.
Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.
WHOOP recovery, strain, sleep and workouts in Claude via official WHOOP OAuth. Free, open source.
| これ Ca Drug Price Transparency | Medplum MCP | Mirobody | Codescene MCP Server | Marrow | WHOOP — MissingMCP | |
|---|---|---|---|---|---|---|
| 動く場所 | クラウドでもパソコンにインストールでも使える | クラウドで動き、インストール不要 | パソコンにインストールが必要 | パソコンにインストールが必要 | パソコンにインストールが必要 | クラウドで動き、インストール不要 |
| キーが必要 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| Claude で + から追加 | いいえ | いいえ | いいえ | いいえ | いいえ | いいえ |
| 基本チェック | 5/5 | 4/4 | 3/3 | 2/3 | 3/3 | 2/4 |
| ライセンス | MIT | Apache-2.0 | Apache-2.0 | NOASSERTION | MIT | MIT |
| 料金 | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし | 登録情報に費用の記載なし |
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
California manufacturer disclosures of prescription drug list-price (WAC) increases and new-drug launch prices — the reports drug makers are required to file under California's Cost Transparency Rx (CTRx) law. Read live; keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
ca_rx_wac_increases(drug?, manufacturer?, ndc?, year?, limit?) — manufacturer disclosures of a WAC increase past the statutory threshold. Returns the increase amount, the WAC after increase, and the effective date.ca_rx_wac_five_year_history(ndc, year?, limit?) — the 5-year WAC history a manufacturer must disclose alongside each increase report for that NDC.ca_rx_new_drug_launches(drug?, manufacturer?, year?, limit?) — manufacturer disclosures of a NEW drug launched with a WAC above the Medicare Part D specialty-drug threshold, with estimated patient population and any breakthrough-therapy/priority-review designation.All three default to searching every available report year (2019–present) when year is omitted, and return a count + years_searched summary before any records; a no-match response names the filters tried rather than an empty array.
Keyless.
Several states run a manufacturer WAC/launch-price disclosure law similar to California's. Surveyed before building, because CLAUDE.md's "one pack per jurisdiction" rule means a second state with genuinely structured public data gets its own pack, not a state argument here — the schemas and even the reporting thresholds differ per state, and a multiplexed pack cannot describe either honestly:
| State | Publishes a structured public dataset? | Status |
|---|---|---|
| California | Yes — open CKAN datasets, queryable, 2019–present | Built here |
| Minnesota | Yes — two fixed Excel snapshot files (price-growth, new-drug), no history API | Public, keyless, file-only; candidate for a separate local-copy pack, not built in this pass |
| Oregon | No — manufacturers submit through an account-gated portal (iReg); no public query/download tool was found | Not buildable without a credential |
| Colorado | No — Division of Insurance posts narrative PDF reports only | Not structured |
| Vermont | No — Green Mountain Care Board / AG publish narrative PDF reports only | Not structured |
| Nevada | No — DHHS publishes narrative PDF reports (diabetes/insulin-focused) only | Not structured |
| Washington | No — HCA/PDAB publish narrative PDF reports and a claims-based affordability dashboard, not manufacturer disclosure records | Not structured |
| Maine | No — MHDO publishes an annual narrative PDF report only | Not structured |
"Not structured" means no CSV/Excel/API was found publishing the underlying manufacturer-filed records — only a narrative PDF report summarizing them, which would require manual transcription rather than ingestion. Re-verify before assuming this is permanent: states have moved from PDF-only to a real dataset before (this is exactly what California's own CTRx program did).
Two header shapes per dataset, and they are not cosmetic. HCAI's "in-progress current year" resource uses snake_case machine column names (manufacturer_name, wac_effective_date, wac_increase_amount as a JSON number). Every CLOSED annual archive (2019 through last full year) uses human Title-Case column names with spaces ("Manufacturer Name", "WAC Effective Date") and stringifies the same amounts — the 5-year-history resource further prefixes them with "$" and commas in BOTH shapes. Matching on one spelling silently drops every year that doesn't use it; every normalizer here reads both.
CKAN's `q` full-text parameter is not a substring filter on the field you think you're searching. Measured 2026-10-18: q=Pfizer against a 1,251-row resource with zero rows naming Pfizer anywhere still returned total: 151 — it ranks relevance across every text column, including long narrative fields like "General Comments", and is capped by that ranking rather than by an exact match. A real hit outside the top-ranked slice could be silently missed. This pack uses datastore_search_sql (also keyless, confirmed live) with an explicit ILIKE on the exact column being searched instead.
Resource ids are resolved live, not hardcoded. The "current year" resource becomes a dated archive every January, the same way CMS's NADAC dataset id rotates (see mcps/drug-prices), and HCAI's own id for it is not guaranteed stable across that rollover. resolveResources() reads CKAN's package_show and classifies every resource by its NAME; a hardcoded last-known-good map (captured 2026-10-18) is the fallback only if that live lookup itself fails.
The 5-year-history dataset can contain overlapping entries for the same NDC. Each filed WAC Increase Report re-states the preceding 5 years of history as of its own effective date, so a drug that had two increases in the same window produces two reports whose history windows overlap. That is a property of what HCAI publishes, not a dedup bug — ca_rx_wac_five_year_history returns every filed history row rather than silently collapsing them.
WAC is the manufacturer's published list price, not what anyone actually pays. For the retail acquisition cost or the Medicare Part B payment limit, see mcps/drug-prices (nadac_price / asp_payment_limit) — this pack answers "what did the manufacturer disclose", not "what does a pharmacy or Medicare pay".
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": { "ca-drug-price-transparency": { "url": "https://gateway.pipeworx.io/ca-drug-price-transparency/mcp" } } }
tools/list at https://gateway.pipeworx.io/ca-drug-price-transparency/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": { "pipeworx": { "url": "https://gateway.pipeworx.io/mcp" } } }
Both URLs reach the same gateway and the same 1863+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/ca_rx_wac_increases \
-H 'Content-Type: application/json' \ -d '{"manufacturer":"Aadi Bioscience"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/ca_rx_wac_increases. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
@pipeworx/mcp-ca-drug-price-transparency is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/ca-drug-price-transparency/mcp endpoint shown above. It needs network access; there is no offline mode.
{
"mcpServers": { "ca-drug-price-transparency": { "command": "npx", "args": ["-y", "@pipeworx/mcp-ca-drug-price-transparency"] } } }
Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": " " } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Ca Drug Price Transparency data" })
The gateway picks the right tool and fills the arguments automatically.
MIT