
Meddata
io.github.anthesiallcPublished by GitHub account anthesiallcv0.2.1Updated Oct 24, 2026
Drug & supplement lookup and interaction checks from free U.S. government health data.
Overview
Lets an assistant look up U.S. drug and supplement data and check interactions between a list of drugs and supplements.
- What you can do
- Wraps the MedData REST API as MCP tools. Tools include search_drugs and get_drug (by RxCUI), get_drug_by_ndc, search_supplements and get_supplement, check_interactions for a mixed list of 2-10 items, assess_routine for a per-pair assessment with sources, timing and food conditions, and get_usage for billing-period usage. assess_routine distinguishes a finding, a source consulted with nothing found, a pair no source covers, and an unresolved item.
- When to use it
- Use it when an assistant needs conversational drug or supplement lookup, or interaction checks that cite the underlying documents. assess_routine suits answers that will be explained or acted on; check_interactions suits a quick flat list.
- Requirements
- A local Python runtime (PyPI package meddata-mcp, run via uvx or pip) and a MedData API key in the MEDDATA_API_KEY environment variable; a free key is available with a 250 calls/month limit. Optional MEDDATA_BASE_URL and MEDDATA_TIMEOUT. Install into a dedicated environment because of a dependency conflict with the MedData API app.
Installation
In SourceWeft
- Open Meddata in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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
check_interactions vs assess_routine
check_interactions returns a flat list of interactions. assess_routine
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:
not_covered and no_finding_in_sources are different answers, and a flat
empty list cannot tell them apart.
assess_routine also takes class_matching (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:
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):
Or install with pip into its own environment:
Note: install into a dedicated environment. The
mcpSDK 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 tohttps://meddata.anthesia.io.MEDDATA_TIMEOUT(optional) — request timeout in seconds, default30.
Client configuration
Claude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
Cursor
Add the same block to ~/.cursor/mcp.json (or the project .cursor/mcp.json).
Smithery (hosted, no install)
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.
LangChain / LangGraph
Any LangChain or LangGraph agent can use these tools through
langchain-mcp-adapters:
LlamaIndex works the same way via its MCP tool spec.
Develop from source
Notes
- Data is for informational purposes only and is not medical advice.
- Interaction data comes from established medical databases; an empty result means none were found in those sources, not that a combination is proven safe.
Source: README.md at commit a0ab4de
Tools
0Version history
1- v0.2.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts