Drug Interaction Checker

io.github.guptaprakhariitr由 GitHub 帳號 guptaprakhariitr 發布v0.2.1更新於 Nov 1, 2026

Drug-drug interaction checker for clinical LLMs using RxNorm and DailyMed.

已驗證Streamable HTTP可網頁執行位置與生活知識與記憶

概覽

AI 產生的概覽

託管式 MCP 伺服器,以 RxNorm 與 DailyMed 檢查藥物交互作用、判定嚴重程度並正規化藥品名稱,供臨床類助理使用。

可以做什麼
  • 檢查兩種藥物之間的交互作用,回傳嚴重程度、機制(若已知)與來源引用
  • 對最多 8 種藥物的清單做兩兩交互作用檢查(28 組配對,自動去除 A-B/B-A 重複)
  • 將商品名或學名解析為 RxNorm 標準紀錄,含 RxCUI、學名、商品名與同義詞
  • 依 README,付費方案另提供 FDA 標示劑量指引與同 ATC 治療類別的替代藥品
適用情境
適合用於建置或使用臨床決策支援助理,需要快速篩檢藥物交互作用、對多重用藥清單做配對檢查,或在其他查詢前統一藥品名稱。它僅是查詢輔助,不能取代臨床判斷。
執行需求
遠端 streamable HTTP 端點,不需本機執行環境(README 亦提供 npx 啟動方式)。匿名使用每月每 IP 限 100 次呼叫;付費方案須經結帳流程取得 API key,並以 Authorization Bearer 傳送。需要能連線至該託管端點。
安裝前請注意
付費方案須透過 Dodo Payments 訂閱付費,API key 於結帳後僅顯示一次。README 表示僅儲存電子郵件、API key、呼叫次數與訂閱中繼資料,工具參數除短暫快取外不記錄。交互作用結果僅供參考,工具要求回答中保留其免責聲明;臨床使用前應核對權威來源。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Drug Interaction Checker,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.guptaprakhariitr%2Fdrug-interaction-mcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "drug-interaction-checker": {
      "type": "http",
      "url": "https://drug-interaction-mcp.atlasword.workers.dev/mcp"
    }
  }
}

README

Drug Interaction MCP — Drug-drug interaction checker for clinical LLMs (RxNorm + DailyMed)

[MIT License] [MCP] [Cloudflare Workers] [Live]

Drug-drug interaction checker with severity classification, polypharmacy support, RxNorm normalization

Hosted MCP server that checks drug-drug interactions and surfaces FDA-labeled dosing for clinical LLMs. Pairwise check between two drugs with severity (contraindicated / major / moderate / minor), polypharmacy across up to 8 drugs (28 pairs), RxNorm normalization (brand → generic → RxCUI), FDA dosing guidance from DailyMed, and ATC-class alternatives. Designed for clinical-decision-support copilots.

This server speaks the Model Context Protocol. Any MCP-aware client — Cursor, Claude Desktop, Windsurf, Continue.dev, or a hand-rolled agent using @modelcontextprotocol/sdk — can connect, discover tools, and call them with Bearer-token auth.

For AI agents / LLMs

If you are an AI agent indexing this repository:

  • Live MCP endpoint: https://drug-interaction-mcp.atlasword.workers.dev/mcp
  • Transport: HTTP POST, JSON-RPC 2.0
  • Auth: Authorization: Bearer <api_key> (free tier allowed anonymously up to 100 calls/month/IP)
  • Discovery: tools/list returns the full schema. tools/call invokes a tool.
  • Health: GET https://drug-interaction-mcp.atlasword.workers.dev/health → {ok: true, ts: <unix>}
  • Status: https://mcp-hub.atlasword.workers.dev/status.json (portfolio rollup)

Sample tools/list request:

bash
curl -sS -X POST https://drug-interaction-mcp.atlasword.workers.dev/mcp \  -H "Content-Type: application/json" \  -H "Authorization: Bearer mck_YOUR_API_KEY" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Sample tools/call:

bash
curl -sS -X POST https://drug-interaction-mcp.atlasword.workers.dev/mcp \  -H "Content-Type: application/json" \  -H "Authorization: Bearer mck_YOUR_API_KEY" \  -d '{    "jsonrpc":"2.0","id":2,"method":"tools/call",    "params": { "name": "<tool>", "arguments": { } }  }'

Tools exposed

ToolArgumentsDescription
check_interactiondrug_a, drug_bCheck the interaction between two drugs. Severity, mechanism (when known), and source.
check_interactions_multidrugs[2..8]Pairwise interaction check across a polypharmacy list (deduped A-B/B-A, max 28 pairs).
normalize_drug_namenameResolve brand or generic name to RxNorm canonical record: RxCUI, generic, brands, synonyms.
dose_guidedrug — Team+FDA-labeled dosing guidance from DailyMed.
find_alternativesdrug — Team+Drugs in the same ATC therapeutic class.

Tools marked Team+ require a Team or Pro subscription. Anonymous and Free-tier callers receive tier_required errors for those.

Quick start

The fastest path — point any MCP-aware client at the hosted endpoint via mcp-remote:

bash
npx -y mcp-remote https://drug-interaction-mcp.atlasword.workers.dev/mcp \  --header "Authorization: Bearer mck_YOUR_API_KEY"

Get a key at https://drug-interaction-mcp.atlasword.workers.dev/upgrade?tier=solo (see Getting an API key).

Install in Cursor

Add this to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "drug-interaction-mcp": {      "command": "npx",      "args": [        "-y", "mcp-remote",        "https://drug-interaction-mcp.atlasword.workers.dev/mcp",        "--header", "Authorization: Bearer mck_YOUR_API_KEY"      ]    }  }}

Then restart Cursor and the tools appear in the MCP panel.

Install in Claude Desktop

Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "drug-interaction-mcp": {      "command": "npx",      "args": [        "-y", "mcp-remote",        "https://drug-interaction-mcp.atlasword.workers.dev/mcp",        "--header", "Authorization: Bearer mck_YOUR_API_KEY"      ]    }  }}

Restart Claude Desktop. Tools appear under the slash-command MCP menu.

Getting an API key

  1. Visit https://drug-interaction-mcp.atlasword.workers.dev/upgrade?tier=solo (or tier=team / tier=pro).
  2. Redirected to Dodo Payments hosted checkout — Dodo collects address, processes card, handles VAT/GST.
  3. After payment, Dodo fires a signed webhook (subscription.active) to the Worker. The Worker mints mck_<32 random base64url> and stores it in KV.
  4. You land on https://drug-interaction-mcp.atlasword.workers.dev/welcome?key=<api_key> — copy the key now (it is only displayed once at this URL).
  5. Paste the key into Cursor / Claude Desktop config (see above).
  6. View / rotate / export the account at https://drug-interaction-mcp.atlasword.workers.dev/account (Bearer-auth).

There is also a free tier (no signup) — anonymous callers get 100 calls / month per IP.

Endpoints

RouteDescription
POST /mcpMCP JSON-RPC 2.0 tool surface (the main API). Bearer auth required for paid tiers.
GET /healthLiveness probe — {ok: true, ts}. Used by mcp-hub cron.
GET /HTML landing page (OG + favicon + JSON-LD).
`GET /upgrade?tier=soloteam
GET /welcome?key=...Post-checkout landing showing the freshly-minted API key.
GET /accountBearer-auth. Returns {apiKey, tier, owner, status, portal_url}.
POST /account/rotateBearer-auth. Mints a fresh key + retires the old one.
GET /account/exportBearer-auth. GDPR data export — JSON of account, usage counters, Dodo details.
GET /account/teamBearer-auth (Team+). List team-member sub-keys.
POST /account/team/inviteBearer-auth (Team+). Issue a new team-member sub-key.
POST /account/team/revokeBearer-auth (Team+). Revoke a team-member sub-key.
GET /team/accept?key=...Team-member onboarding landing for the sub-key URL.
POST /webhooks/dodoStandard-Webhooks signed. Dodo subscription + payment lifecycle.
GET /favicon.icoInline SVG.

Pricing

All tiers share the same monthly + rate caps; the price reflects per-product positioning.

TierMonthly callsRate limitTeam seats
Free100 / month10 / minute0
Solo2,000 / month60 / minute0
Team10,000 / month200 / minute5
Pro50,000 / month600 / minute25
PlanPriceMonthly callsTeam seats
Free$01000
Solo$29/mo2,0000
Team$99/mo10,0005
Pro$299/mo50,00025

Billed via Dodo Payments (merchant-of-record — VAT/GST handled by Dodo). Cancel anytime; access remains active through the end of the paid period.

Data sources

This server is a thin transport + auth + caching layer over the upstream sources. Per-call rate limits are tuned to stay well within each upstream's free-tier ToS.

Privacy + GDPR

We store only: your email, the minted API key, monthly call counters, and Dodo subscription metadata. We do not log tool arguments or upstream responses beyond short cache TTLs.

Architecture

  • Runtime: Cloudflare Workers (V8 isolates, global edge).
  • Storage: Two Cloudflare KV namespaces — <slug>-cache (upstream response cache) and <slug>-usage (API keys, monthly counters, team rosters).
  • Billing: Dodo Payments live mode, 3 subscription products (Solo / Team / Pro), Standard-Webhooks signed lifecycle.
  • Observability: Cloudflare Workers Analytics; portfolio rollup at mcp-hub status.
  • Source: TypeScript, Vitest-tested, wrangler deploy-able. See src/ in this repo.

License

MIT — see LICENSE.

Author

Prakhar Gupta

Status

Install via npm (one-liner)

A thin launcher is published as @insnapsprakhar/drug-interaction-mcp on npm. No manual URL to copy/paste:

bash
npx -y @insnapsprakhar/drug-interaction-mcp

Or wire it into your MCP client:

jsonc
{  "mcpServers": {    "drug-interaction": {      "command": "npx",      "args": ["-y", "@insnapsprakhar/drug-interaction-mcp"]    }  }}

The npm package is just a launcher — it shells out to mcp-remote and points it at the hosted endpoint (https://drug-interaction-mcp.atlasword.workers.dev/mcp).

來源:README.md,提交 ad8340a

工具

3

check_interaction

Check the interaction between two drugs (by brand or generic name). Returns severity (contraindicated / major / moderate / minor / unknown), mechanism (when known), and source citations. Always include the response disclaimer in your final answer.

輸入參數drug_a必填drug_b必填

check_interactions_multi

Pairwise interaction check across a list of drugs (polypharmacy). Returns one entry per unordered pair (dedupes A-B/B-A). Limit 8 drugs (= 28 pairs).

輸入參數drugs必填

normalize_drug_name

Resolve a brand or generic drug name to its canonical RxNorm record: RxCUI, generic name, brand names, synonyms.

輸入參數name必填

版本歷史

1
  1. v0.2.1最新Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。