Meddata Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Meddata Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
| Tool | What it does |
|---|---|
search_drugs | Search drugs by brand or generic name; returns RxCUI + details |
get_drug | Full drug profile by RxCUI |
get_drug_by_ndc | Drug profile by NDC package code |
search_supplements | Search supplements by name; returns supplement IDs |
get_supplement | Full supplement fact sheet by ID |
check_interactions | Interactions across a mixed list of 2-10 drugs/supplements |
get_usage | Current billing period usage and plan limit |
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":"[email protected]"}'The key comes back in the api_key field of the response.
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 --httpOr install with pip into its own environment:
pip install meddata-mcp
MEDDATA_API_KEY=md_your_key meddata-mcpNote: install into a dedicated environment. ThemcpSDK requires a newerstarlettethan the MedData API app pins, so the two will conflict if installed together.
Environment variables:
MEDDATA_API_KEY (required) — your MedData API key.MEDDATA_BASE_URL (optional) — defaults to https://meddata.anthesia.io.MEDDATA_TIMEOUT (optional) — request timeout in seconds, default 30.Add to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"meddata": {
"command": "uvx",
"args": ["meddata-mcp"],
"env": { "MEDDATA_API_KEY": "md_your_key" }
}
}
}Add the same block to ~/.cursor/mcp.json (or the project .cursor/mcp.json).
The server is hosted on Smithery, so MCP clients that support Smithery can connect without installing anything. You provide your MedData API key in the Smithery config and it routes to the server.
Any LangChain or LangGraph agent can use these tools through langchain-mcp-adapters:
# pip install langchain-mcp-adapters langgraph "langchain[anthropic]"
from langchain_mcp_adapters.client import MultiServerMCPClient
client = MultiServerMCPClient(
{
"meddata": {
"transport": "stdio",
"command": "uvx",
"args": ["meddata-mcp"],
"env": {"MEDDATA_API_KEY": "md_your_key"},
}
}
)
tools = await client.get_tools()
# hand `tools` to a LangGraph/LangChain agent, e.g.
# from langgraph.prebuilt import create_react_agent
# agent = create_react_agent("anthropic:claude-opus-4-8", tools)LlamaIndex works the same way via its MCP tool spec.
git clone https://github.com/anthesiallc/meddata-mcp && cd meddata-mcp
python -m venv .venv
.venv/Scripts/python -m pip install -e ".[http]" # Windows; [http] adds uvicorn for --http
# .venv/bin/pip install -e ".[http]" # macOS/Linux
MEDDATA_API_KEY=md_your_key .venv/Scripts/python -m meddata_mcp.servermeans none were found in those sources, not that a combination is proven safe.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.