OpenFDA MCP Server
Related Servers
Alternatives to OpenFDA MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceA comprehensive MCP server that provides access to U.S. FDA public datasets via the openFDA API, enabling querying of drug adverse events, labeling, recalls, approvals, shortages, NDC directory, and medical device regulatory data.1026-
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to query U.S. FDA public datasets, including drug adverse events, labeling, recalls, approvals, shortages, NDC directory, and medical device regulatory information.10MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for clinical and pharmaceutical data, enabling search of ClinicalTrials.gov, PubMed, FDA, and ICH guidelines without API keys.MIT
- AlicenseNot gradedqualityDmaintenanceThis MCP server provides authoritative medical data from FDA, WHO, PubMed, RxNorm, and Google Scholar, enabling drug information lookup, health statistics retrieval, medical literature searching, and clinical guidelines access directly in AI workflows.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides comprehensive medical information by querying authoritative APIs including FDA, WHO, PubMed, RxNorm, and Australia's PBS, enabling drug searches, health statistics, medical literature, drug nomenclature, and PBS subsidy queries.MIT
- AlicenseBqualityCmaintenanceAn MCP server that provides comprehensive medical information by querying multiple authoritative medical APIs including FDA, WHO, PubMed, Google Scholar, and RxNorm.1174 npm122MIT
TDQS
Scored across 15 tools
Each tool maps to a distinct FDA dataset (labels, adverse events, NDC, 510(k), MDR, shortages, Purple Book), so selection is mostly clear. The only real overlap is search_fda_orange_book vs search_fda_orange_book_patents vs search_fda_drug_patent_expiry, where the unified patent-expiry view partially duplicates the other two — descriptions mitigate but don't erase this.
Nearly all tools follow a search_<domain>_<resource> snake_case pattern (search_drug_labels, search_device_510k, search_fda_purple_book). Minor deviations exist: bare 'info' and 'search_drugs_at_fda' (plural) break the pattern, and the prefix ordering alternates between drug-first, device-first, and fda-first.
Fifteen tools is well within a reasonable range and each corresponds to a real, distinct OpenFDA endpoint. Nothing feels padded — the count is justified by the breadth of FDA datasets (drugs, devices, biologics, patents).
Strong coverage of drugs, devices, biologics, patents, recalls, and adverse events with both search and retrieve-by-ID paths. Gaps remain: no food/dietary-supplement/cosmetic/tobacco endpoints that OpenFDA offers, and no generic cross-endpoint query, but core drug/device workflows are covered.