MCP.Market

Meddata MCP server

by anthesiallc·io.github.anthesiallc/meddata·v0.2.1

Drug & supplement lookup and interaction checks from free U.S. government health data.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

0 stars26 downloads/wk

Reviews

Write one

Nobody has reviewed Meddata yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Meddata tools (7)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • check_interactions

    Check interactions across a mixed list of drugs and supplements.

  • get_drug

    Get the full profile for a drug by its RxCUI.

  • get_drug_by_ndc

    Get a drug profile by its NDC (National Drug Code) package code.

  • get_supplement

    Get the full fact sheet for a supplement by its ID.

  • get_usage

    Show this API key's current billing period usage and plan limits.

  • search_drugs

    Search for drugs by brand or generic name.

  • search_supplements

    Search for dietary supplements by name.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 16 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Meddata compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers
Tools
7
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
26
more than 13% of 12,191 servers with a package

What its tools let an agent do: 7 read

Install Meddata in Claude Code, Cursor or VS Code

claude mcp add meddata -- uvx meddata-mcp
Add to Cursor

What the publisher says

From the Meddata repository's README, as published. We do not edit it. Read it on GitHub

MedData MCP Server

mcp-name: io.github.anthesiallc/meddata

A Model Context Protocol server that exposes the MedData API as tools, so any MCP client (Claude Desktop, Cursor, ChatGPT connectors, or an agent framework) can look up drug and supplement data and check interactions conversationally.

It's a thin wrapper: each tool maps to one MedData REST endpoint. All the data work happens in the API.

Tools

checkinteractions vs assessroutine

checkinteractions returns a flat list of interactions. assessroutine returns the reasoning: what each submitted name resolved to, what was consulted for every pair, and the document behind each finding. Reach for it when the answer will be explained or acted on rather than just displayed.

The distinction that matters most is in pairs_checked[].status:

notcovered and nofindinginsources are different answers, and a flat empty list cannot tell them apart.

assessroutine also takes classmatching (default off). With it on, a drug matches the therapeutic classes a supplement record names, not only the drug names it lists; those findings carry basis.level: "class" and name the class, so an inferred match stays distinguishable from an explicit one. Findings also carry basis.level (formulation / ingredient / class) saying how closely the source matches what was submitted, three-state timing and food conditions where silence is not_documented rather than "no effect", and references[] with the document version and the verbatim passage.

Get an API key

Free tier is 250 calls/month, no credit card:

curl -X POST https://meddata.anthesia.io/api/v1/signup \
  -H 'Content-Type: application/json' \
  -d '{"email":"you@example.com"}'

The key comes back in the api_key field of the response.

Install and run

The easiest way is with uv (no manual venv needed):

# stdio transport (default — for Claude Desktop, Cursor, most local clients)
MEDDATA_API_KEY=md_your_key uvx meddata-mcp

# streamable-HTTP transport (for remote / web clients)
MEDDATA_API_KEY=md_your_key uvx meddata-mcp --http

Or install with pip into its own environment:

pip install meddata-mcp
MEDDATA_API_KEY=md_your_key meddata-mcp

Note: install into a dedicated environment. The mcp SDK requires a newer

starlette than the MedData API app pins, so the two will conflict if installed

together.

Environment variables:

  • MEDDATAAPIKEY (required) — your MedData API key.
  • MEDDATABASEURL (optional) — defaults to https://meddata.anthesia.io.
  • MEDDATA_TIMEOUT (optional) — request timeout in seconds, default 30.

Client configuration

Claude Desktop

Add to claudedesktopconfig.json (Settings → Developer → Edit Config):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Meddata: common questions

Is Meddata MCP server safe?
Mostly: it is graded B (80/100). Read the Meddata safety report
How do I install Meddata?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Meddata need an API key?
Yes. The registry entry asks for MEDDATA_API_KEY.
Is Meddata maintained?
The last commit was 55 days ago (2026-09-10). The latest release is v0.2.1.
How does Meddata compare with other MCP servers?
safety score 80/100 (higher than 60% of 48,255 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.