Drug Interaction Checker logo

Drug Interaction Checker

Checks drug interactions, normalizes names, provides DailyMed dosing, and finds ATC-class alternatives through MCP.

Install Drug Interaction Checker

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://drug-interaction-mcp.atlasword.workers.dev/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Overview

Drug Interaction Checker MCP server connects clinical LLMs to RxNorm, DailyMed, and openFDA data through MCP tools. It checks pairwise or multi-drug interactions, resolves brand and generic names, returns FDA-labeled dosing guidance, and identifies alternatives in the same ATC class. Use it for medication-review workflows and clinical decision-support copilots that need structured drug information. The hosted endpoint uses HTTP JSON-RPC and Bearer-token authentication, with anonymous access limited to 100 calls per month per IP.

Use cases

  • Check interactions across a patient medication list
  • Normalize brand and generic drug names
  • Retrieve FDA-labeled dosing guidance
  • Find alternatives within an ATC class

Key features

  • Pairwise interaction severity and mechanism lookup
  • Polypharmacy checks for up to eight drugs
  • RxNorm name normalization with RxCUI details
  • DailyMed FDA-labeled dosing guidance
  • ATC therapeutic-class alternatives
  • HTTP JSON-RPC MCP endpoint

Tools5

What Drug Interaction Checker lets your agent do. Expand a tool for its parameters.

Self-reported~108 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

5/5 checks healthy over the last 30d

Supply-chain signal

1 high-severity advisory on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 1High 0Medium 0Low 0

Scanned 9/10/2026 via OSV.dev · https://drug-interaction-mcp.atlasword.workers.dev/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit4mo agoMost recent push to the default branch.
Tools exposed5Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Drug Interaction Checker works

What Drug Interaction Checker does

Drug Interaction Checker MCP server exposes medication lookup and clinical reference operations through the Model Context Protocol. It is designed for agents that need to examine drug combinations, standardize names, retrieve labeled dosing information, or suggest drugs within the same therapeutic class.

The service uses RxNorm from the U.S. National Library of Medicine for drug normalization and interaction-related lookups. DailyMed supplies FDA-labeled dosing guidance, while openFDA Drug Label is listed among the upstream public-domain sources. The hosted deployment runs at https://drug-interaction-mcp.atlasword.workers.dev/mcp.

How it works

Clients send MCP JSON-RPC 2.0 requests over HTTP POST. Tool discovery is available through tools/list, and individual operations are invoked with tools/call. Requests can include an Authorization: Bearer <api_key> header. Anonymous callers can use the free tier for up to 100 calls per month per IP; paid tiers provide higher monthly and rate limits.

check_interaction compares two drugs and reports a severity category—contraindicated, major, moderate, or minor—along with the mechanism when known and its source. check_interactions_multi examines a list of two to eight drugs pairwise, removes duplicate directions such as A-B and B-A, and evaluates up to 28 pairs.

Setup and configuration

The quickest connection method is mcp-remote pointed at the hosted MCP endpoint. Supply the Bearer token as a request header, then add the resulting command to an MCP client configuration. The README provides configurations for Cursor and Claude Desktop; after restarting either client, the tools should be available in its MCP interface.

A key can be obtained through the hosted upgrade flow for Solo, Team, or Pro access. The service also supports anonymous free-tier requests. The endpoint exposes a /health route for liveness checks. No local database or application-specific environment variable is described for client setup.

Tools and capabilities

  • check_interaction: inspect a two-drug combination and return severity, mechanism when available, and source.
  • check_interactions_multi: review polypharmacy lists containing two to eight drugs.
  • normalize_drug_name: map a brand or generic name to an RxNorm record with RxCUI, generic name, brands, and synonyms.
  • dose_guide: retrieve FDA-labeled dosing guidance from DailyMed. This tool requires Team or Pro access.
  • find_alternatives: find drugs in the same ATC therapeutic class. This tool also requires Team or Pro access.

The Drug Interaction Checker MCP server is suited to medication reconciliation assistants, drug-information agents, and clinical decision-support copilots that need source-backed lookups rather than an embedded medication database.

Limitations and notes

The Drug Interaction Checker MCP server is a transport, authentication, and caching layer over upstream sources, not an independent clinical knowledge base. Interaction results depend on the available RxNorm, DailyMed, and openFDA data.

Anonymous and Free-tier callers receive tier_required errors for the dosing and alternatives tools. Usage is subject to monthly call caps and per-minute rate limits: Free provides 100 calls per month, while Solo, Team, and Pro provide 2,000, 10,000, and 50,000 calls respectively. Treat returned information as reference data for an appropriate clinical workflow.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Drug Interaction Checker

Drug Interaction Checker is an MCP server that connects clinical LLMs to RxNorm, DailyMed, and openFDA data. Its main tools check pairwise and multi-drug interactions, normalize drug names, retrieve FDA-labeled dosing guidance, and find alternatives in the same ATC therapeutic class.

Install it by configuring an MCP client to run `mcp-remote` against the hosted endpoint and pass a Bearer API key. The README includes setup examples for Cursor and Claude Desktop, followed by a client restart to expose the tools.

Yes, Drug Interaction Checker works with Cursor through `mcp-remote`. Add the provided server entry to `~/.cursor/mcp.json`, replace the placeholder token with a valid key, and restart Cursor so the tools appear in its MCP panel.

The polypharmacy tool accepts between two and eight drugs and checks up to 28 unique pairs. It removes duplicate directional combinations, so A-B and B-A are not evaluated separately.

The `dose_guide` and `find_alternatives` tools require Team or Pro access.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewDrug Interaction Checker AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/drug-interaction-checker?style=directory)](https://allmcps.com/mcp/drug-interaction-checker)
HTML Embed
<a href="https://allmcps.com/mcp/drug-interaction-checker"><img src="https://allmcps.com/api/badge/drug-interaction-checker?style=directory" alt="Drug Interaction Checker on AllMCPs" /></a>