What it does
fdarecords is a small client for the openFDA API. It provides seven tools for two lookup tasks: finding drug information (label text, the Drugs@FDA application behind a product, and the application numbers filed under a brand or generic name) and tracing a medical device from its submission number to its regulatory class. One tool, screen_for_rwe_signals, sweeps drug labels for real-world-evidence terms and is experimental. De Novo numbers are searched through the 510(k) endpoint, because openFDA has no De Novo endpoint of its own.
It suits anyone who repeatedly needs these FDA lookups and would rather not search the FDA portal by hand. Every tool returns null when a query matches nothing. Transient failures such as timeouts, connection errors, 429 and 5xx responses are retried twice with backoff and then raised as errors, so a null always means no match rather than a failed request.
Each tool runs as a subcommand of a CLI that takes one JSON argument string and prints the result. It can also run as an MCP server, with a client configuration, or in Docker. The base URL defaults to https://api.fda.gov and can be changed with OPENFDA_BASE_URL. An openFDA API key is optional and raises rate limits; every tool works without one. The CLI exits with 0 on success, 1 on a runtime error and 2 on a usage error.
Limitations and requirements
screen_for_rwe_signals is experimental and unvalidated; its hits are candidates for human review, not findings. HDE (H) numbers are not in openFDA, so their lookups return null, and validate_device_application reports class III for them as regulatory inference rather than data. Submission numbers with an unrecognized prefix are rejected. Some endpoint paths are pattern-derived rather than pinned to the openFDA index. Optional OPENFDA_API_KEY is needed only for higher rate limits.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/fdarecords
openFDA identifier resolution: drug labels and applications, device submissions, classification.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it