openFDA MCP by usefulapi
REMOTE · OPENFDA.USEFULAPI.IO
Search openFDA drug, device, food and adverse-event datasets.
Available components
Last scanned (13 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −47
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_device_clearance_class_recalls_and_events” functional
- New prompt “find_food_recalls_and_food_adverse_events” functional
- New prompt “find_the_most_reported_side_effects_of_a_drug” functional
- New prompt “look_up_approved_drug_products_and_drug_codes” functional
- New prompt “look_up_drug_recalls_and_shortages” functional
- New prompt “review_a_drug_s_prescribing_information” functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.2 → 1.31.0 functional
- 30 Oct 26 0
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 +1
- Server version: 1.29.0 → 1.30.0 functional
- Server version: 1.28.0 → 1.29.0 functional
- 28 Oct 26 0
- Server version: 1.26.0 → 1.28.0 functional
- 27 Oct 26 0
- Server version: 1.25.0 → 1.26.0 functional
- 25 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.3 → 1.23.0 functional
- Server version: 1.22.0 → 1.22.3 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://openfda.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of openfda.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://openfda.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/openfda/ |
| http (plaintext) | http://openfda.usefulapi.io/mcp | Inconclusive | 302 | http://openfda.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
openfda_count Count/aggregate over an openFDA dataset ~220
openFDA's most valuable feature: aggregate over any dataset by a field to get a top-terms histogram (returns `results: [{term, count}]` instead of records). Use the '.exact' field suffix to count whole phrases. Example: endpoint 'drug/event', field 'patient.reaction.reactionmeddrapt.exact', search 'patient.drug.medicinalproduct:"aspirin"' → the most common reactions reported for aspirin.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | The openFDA endpoint to query, e.g. 'drug/event', 'device/510k', 'food/enforcement'. |
| field | string | yes | The field to count/aggregate on (required), e.g. 'patient.reaction.reactionmeddrapt.exact' or 'classification'. Add '.exact' to count whole phrases rather than tokens. |
| limit | integer | – | Max number of distinct terms to return (1–1000). |
| search | string | – | Optional Lucene filter applied before aggregation (same syntax as the search tools). |
No output schema declared.
No examples provided.
openfda_query Query any openFDA endpoint (generic) ~328
Generic escape hatch to query ANY supported openFDA endpoint with the full parameter set — covers the less-common datasets (device/pma, device/registrationlisting, device/udi, device/covid19serology, drug/orangebook, other/nsde, other/substance, tobacco/problem, etc.). Use the named search tools for the common datasets; use this for everything else or for advanced queries. openFDA REST API.
| Name | Type | Req | Description |
|---|---|---|---|
| count | string | – | Optional field to aggregate on (returns `results: [{term, count}]`); add '.exact' for whole phrases. |
| endpoint | string | yes | The openFDA endpoint to query, e.g. 'drug/event', 'device/510k', 'food/enforcement'. |
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_device_510k Search 510(k) premarket clearances ~220
Search 510(k) premarket notification clearances: devices cleared for market as substantially equivalent to a predicate, with applicant, decision, product code and dates. openFDA device/510k endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_device_classification Search device classification ~218
Search the FDA device classification database: a device type's product code, device class (I/II/III), regulation number, medical specialty and submission requirements. openFDA device/classification endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_device_events Search device adverse-event reports (MAUDE) ~205
Search the MAUDE database: medical device adverse events — reported injuries, deaths and malfunctions involving medical devices. openFDA device/event endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_device_recalls Search device recalls ~211
Search medical device recalls: recalled devices with the reason, recalling firm, classification, product code and status. openFDA device/recall endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_drug_events Search drug adverse-event reports (FAERS) ~220
Search the FDA Adverse Event Reporting System (FAERS): reports of drug side effects, adverse reactions and medication errors submitted to the FDA. Returns individual case reports. openFDA drug/event endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_drug_labels Search drug product labels (SPL) ~217
Search Structured Product Labeling (SPL): the official prescribing information for drugs — indications, warnings, dosage, adverse reactions, drug interactions and more. openFDA drug/label endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_drug_ndc Search the National Drug Code directory ~223
Search the National Drug Code (NDC) directory: every drug product's code, name, dosage form, route, active ingredients, marketing status and labeler. openFDA drug/ndc endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_drug_recalls Search drug recall enforcement reports ~212
Search drug recall enforcement reports: recalled drug products with the reason, classification (Class I/II/III), recalling firm, distribution and status. openFDA drug/enforcement endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_drug_shortages Search drug shortages ~203
Search current and resolved drug shortages: the affected product, status, reason, availability and related dates. openFDA drug/shortages endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_drugsfda Search Drugs@FDA approved products ~218
Search Drugs@FDA: FDA-approved drug products and their applications (NDA/ANDA/BLA), sponsors, approval dates, products and submissions. openFDA drug/drugsfda endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_food_events Search food/supplement/cosmetic adverse events (CAERS) ~216
Search the CFSAN Adverse Event Reporting System (CAERS): adverse events and product complaints for foods, dietary supplements and cosmetics. openFDA food/event endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
openfda_search_food_recalls Search food recall enforcement reports ~211
Search food recall enforcement reports: recalled food products with the reason, classification (Class I/II/III), recalling firm, distribution state and status. openFDA food/enforcement endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of records to return (1–1000). Omit for the API default of 1. |
| search | string | – | Lucene-style query over this dataset's fields: 'field:term', AND with '+AND+', OR with a space, exact phrase via a '.exact' field suffix with quotes, ranges as '[low+TO+high]' (dates like '[20040101+… |
| skip | integer | – | Number of records to skip, for pagination (0–25000; skip+limit reaches up to ~26000 records). |
| sort | string | – | Sort order, as `field:asc` or `field:desc`, e.g. 'receivedate:desc'. |
No output schema declared.
No examples provided.
How do I install the openFDA MCP by usefulapi server?
openFDA MCP by usefulapi is a hosted endpoint at https://openfda.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · openfda.usefulapi.io
claude mcp add --transport http io-usefulapi-openfda 'https://openfda.usefulapi.io/mcp'
What is the openFDA MCP by usefulapi server?
openFDA MCP by usefulapi is listed in the public MCP registry as io.usefulapi/openfda. Search openFDA drug, device, food and adverse-event datasets. This page covers its hosted endpoint (https://openfda.usefulapi.io/mcp).
Is the openFDA MCP by usefulapi server safe to use?
openFDA MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the openFDA MCP by usefulapi server expose?
openFDA MCP by usefulapi exposes 14 tools: openfda_search_drug_events, openfda_search_drug_labels, openfda_search_drug_ndc, openfda_search_drug_recalls, openfda_search_drugsfda, and 9 more. Their descriptions and schemas cost roughly 3,122 tokens of context every time the server is loaded.
Does the openFDA MCP by usefulapi server require authentication?
Its publisher declares no required credentials for openFDA MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the openFDA MCP by usefulapi server still maintained?
openFDA MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the openFDA MCP by usefulapi server?
VerifyMCP ran 4 checks on openFDA MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about openFDA MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.