io.github.cyanheads/openfda-mcp-server
v0.8.1Query FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP.
Endpoint health
online- Last checked
- 11/20/2026, 9:18:24 AM
- Latency
- 248 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.cyanheads%2Fopenfda-mcp-server
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.cyanheads/openfda-mcp-server": {
"url": "https://openfda.caseyjhand.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
14 shown · authentication unknown
Openfda Count Values
openfda_count_values
Aggregate and tally unique values for any field across any openFDA endpoint. Returns ranked term-count pairs sorted by count descending; a date field tallies one term per distinct YYYYMMDD date, ranked the same way. Pair with openfda_search_adverse_events, openfda_search_drug_approvals, openfda_search_device_clearances, openfda_search_recalls, openfda_get_drug_label, or openfda_lookup_ndc when sample records help interpret the aggregates.
Schema valid · SHA-256 59fead289863…
View input schema
{ "type": "object", "properties": { "endpoint": { "type": "string", "enum": [ "drug/event", "drug/label", "drug/enforcement", "drug/ndc", "drug/drugsfda", "drug/shortages", "food/event", "food/enforcement", "device/event", "device/510k", "device/pma", "device/recall", "device/enforcement", "device/classification", "device/registrationlisting", "device/udi", "device/covid19serology", "animalandveterinary/event", "tobacco/problem", "other/substance" ], "description": "Full openFDA endpoint path (e.g. \"drug/event\", \"device/classification\")" }, "count": { "type": "string", "minLength": 1, "pattern": "\\S", "description": "Field to count. openfda_describe_fields gives the verified expression per field as countAs (null = not countable in any form). Otherwise: append .exact for whole-phrase counting of free-text fields (e.g. \"patient.reaction.reactionmeddrapt.exact\"); count identifier fields openFDA already indexes as keywords (product_ndc, application_number, pma_number) bare — .exact on those is rejected as not countable. A date field (receivedate, report_date, decision_date) is counted bare and yields one term per distinct YYYYMMDD date." }, "search": { "description": "Filter query to scope the count (e.g. patient.drug.medicinalproduct:\"metformin\"). Omit to count across every record in the endpoint. Separate clauses with spaces. A \"+\" written in the URL style of openFDA's examples also reads as a space where it separates: beside AND, OR, NOT, or TO, after a closing quote, paren, or bracket, or between a term and the next \"field:\" prefix (a:\"x\"+AND+b:\"y\", [20200101+TO+20201231], c:x+d:y). In a query that marks a clause required with a leading +field:, only the AND/OR/NOT/TO positions read that way. Any other \"+\" is sent as written, and inside a quoted phrase \"+\" is a literal plus sign. Double quotes, parentheses, and range brackets must balance, and the query must not end on a backslash — each is rejected before the request.", "type": "string", "minLength": 1, "pattern": "\\S" }, "limit": { "default": 100, "type": "integer", "minimum": 1, "description": "Number of top terms to return. truncated reports whether more distinct terms exist beyond it, except at 1000 — openFDA's own count maximum — where openFDA offers no way to tell. A date field is the exception: openFDA sends every date, so the tool ranks them all and truncated is exact at any limit; scope search to at most limit dates to list each one. Default 100; a larger value returns at most 1000 and says so." } }, "required": [ "endpoint", "count" ], "$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": false }
Connections
streamable-http
https://openfda.caseyjhand.com/mcp