F
licenseNot graded
qualityD
maintenanceEnables querying FDA drug approvals, device clearances (510(k)), recalls, and adverse events via the openFDA API, providing tools for clinical and pharmaceutical research.
1
-
com.blackswancausallabs/openfda-mcp
OfficialRelated Servers
Alternatives to com.blackswancausallabs/openfda-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides LLM-optimized access to FDA data through the OpenFDA API and direct regulatory decision document retrieval, covering all 21 OpenFDA endpoints plus 510(k) summaries, De Novo decisions, and PMA approvals.41MIT
- AlicenseAqualityDmaintenanceEnables LLMs to search FDA drug labels and adverse event data via the OpenFDA API, supporting natural language queries for drug safety information.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables querying FDA medical device regulatory databases including 510(k) clearances, PMA approvals, recalls, and adverse events through natural language.2 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to query and analyze FDA adverse events, drug labels, medical device clearances, and other public health datasets through natural language commands.14-
- AlicenseNot gradedqualityAmaintenanceQuery FDA data on drugs, food, devices, and recalls via openFDA. Provides 12 tools for searching adverse events, drug labels, recalls, and more.135 npm4Apache 2.0
TDQS
A3.9/5.0
Scored across 7 tools
Disambiguation5/5
Each tool targets a distinct resource/action: drug label search, application metadata lookup, name-to-application resolution, RWE signal screening, device submission lookup, product code classification, and full validation. The drug and device groups are clearly separated, and descriptions clarify any potential overlap (e.g., validate_device_application explicitly chains the other two device tools).
Naming Consistency4/5
All tool names follow a verb-first, snake_case convention (search, lookup, resolve, screen, classify, validate), but the noun phrases vary in structure: some are direct objects (drug_label, device_submission), some use prepositions (drug_to_application, for_rwe_signals). This is mostly consistent and readable, with minor deviations.
Tool Count5/5
Seven tools is well-scoped for covering both drug-related (labels, applications, name resolution, RWE signals) and device-related (submissions, product codes, validation) workflows. Each tool serves a clear purpose without bloat.
Completeness4/5
The core workflows are covered: drug label search, drug name-to-application resolution, application metadata retrieval, RWE signal screening, device submission lookup, product code classification, and full validation. Minor gaps exist, such as no device search by name and no adverse event data, but the primary lifecycle is well supported.
Maintenance
ActivitySlowing
ResponsivenessNo issues