Drug Interaction Checker MCP Server

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

Remote serverstreamable-httpTypeScript

What is the Drug Interaction Checker MCP server?

Drug-drug interaction checker for clinical LLMs using RxNorm and DailyMed. Exposed over MCP by the drug interaction checker mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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.

Its toolset

Everything the assistant can do here goes through one of these:

  • check_interaction — drug_a, drug_b
  • check_interactions_multi — drugs[2..8]
  • normalize_drug_name — name
  • dose_guide — drug — Team+
  • find_alternatives — drug — Team+

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Drug Interaction Checker's toolset — check_interaction, check_interactions_multi, normalize_drug_name and 2 more — is a fair guide to whether it matches your workflow. It is maintained by guptaprakhariitr; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Drug Interaction Checker's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the drug interaction checker mcp server does with a few real requests.

Available tools

ToolWhat it does
check_interactiondrug_a, drug_b
check_interactions_multidrugs[2..8]
normalize_drug_namename
dose_guidedrug — Team+
find_alternativesdrug — Team+

How to install the Drug Interaction Checker MCP server

Or wire it into your MCP client:

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

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Drug Interaction Checker to check interaction.
  • Use Drug Interaction Checker to check interactions multi.
  • Use Drug Interaction Checker to normalize drug name.

Frequently asked questions

It connects Drug Interaction Checker to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (check_interaction, check_interactions_multi, normalize_drug_name, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Drug Interaction Checker directly.