Home / MCP registry index / io.usefulapi/openfda
openFDA MCP by usefulapi
io.usefulapi/openfda in the official MCP registry.
Endpoint https://openfda.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Search openFDA drug, device, food and adverse-event datasets.
We read its 14 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
openfda_search_drug_events openfda_search_drug_labels openfda_search_drug_ndc openfda_search_drug_recalls openfda_search_drugsfda openfda_search_drug_shortages openfda_search_device_events openfda_search_device_510k openfda_search_device_recalls openfda_search_device_classification openfda_search_food_events openfda_search_food_recalls openfda_count openfda_query
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-openfda)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.