This post is from the RegDataLab team. RegDataLab is the hosted MCP server used in the second half; the first half covers the free openFDA options.
If you search for an "openFDA MCP server" you'll find several good ones. They wrap the openFDA HTTP API so Claude, ChatGPT or Cursor can query drug labels, adverse events, recalls, NDC codes and 510(k) decisions.
Then you ask the question a quality or supplier team actually asks, "has this manufacturer had an FDA warning letter or a bad inspection?", and the agent comes back empty or guesses. This post explains why, and shows how to wire the missing FDA data into an MCP client in a couple of minutes.
What openFDA has, and what it doesn't
openFDA publishes one JSON endpoint per dataset. Its download index covers drug, device and food files: adverse events, labels, the NDC directory, Drugs@FDA, shortages, the Orange Book, recall enforcement reports, 510(k) and PMA decisions, device classification, registration and listing, UDI, and food, cosmetic, veterinary and tobacco reports.
These are not openFDA endpoints:
| Data | Where FDA publishes it |
|---|---|
| Inspection classifications (NAI, VAI, OAI) | FDA Data Dashboard |
| Form 483 citations (CFR section + short text) | FDA Data Dashboard |
| Posted Form 483 documents | OII FOIA Electronic Reading Room |
| Warning letters | fda.gov warning letter pages |
| Import alerts, import refusals | Import alert pages, Data Dashboard |
| Debarments | FDA debarment list |
So an MCP server built only on openFDA can't answer inspection or enforcement questions, however good it is. The second problem is names: FDA files records under each site's legal name, so a search for "Baxter" on FDA's own sites misses records filed under Hillrom or Welch Allyn.
Option 1: an openFDA MCP server (free; labels, adverse events, recalls)
If your use case is pharmacovigilance or label lookup, an openFDA server is the simpler choice. For example, the open-source cyanheads/openfda-mcp-server runs locally:
claude mcp add openfda-mcp-server -- npx -y @cyanheads/openfda-mcp-server
It needs no key for light use. openFDA allows 1,000 requests a day per IP without a key and 120,000 a day with a free key (open.fda.gov). You can also call the openFDA API directly, and FDA's own Data Dashboard and warning letter page are free to search by hand.
Option 2: add inspections, 483s and warning letters with RegDataLab
RegDataLab is a hosted MCP server at https://www.regdatalab.com/mcp (Streamable HTTP). It has 52 tools: 51 read-only tools over 35 public FDA datasets, plus a submit_feedback tool. It uses openFDA datasets where they apply, adds the Data Dashboard, warning letter, reading room, import and debarment data, and matches records to a company family and its sites. Every FDA record links back to its FDA source. It does not carry everything openFDA does (the Orange Book, for one), and it has no 483s that FDA hasn't published.
Claude Code
claude mcp add --transport http --scope user regdatalab https://www.regdatalab.com/mcp
Run /mcp, pick regdatalab and choose Authenticate. For CI or a machine with no browser, send a key as a header instead:
claude mcp add regdatalab https://www.regdatalab.com/mcp \
--transport http \
--header "Authorization: Bearer YOUR_API_KEY" \
--scope user
Cursor
Add to ~/.cursor/mcp.json, then open Settings > MCP and click Connect:
{
"mcpServers": {
"regdatalab": {
"url": "https://www.regdatalab.com/mcp"
}
}
}
Cline
Cline uses an API key in a header. Add this to ~/.cline/data/settings/cline_mcp_settings.json, or open Cline's MCP Servers UI, choose Streamable HTTP on the Remote Servers tab, and enter the same URL and header:
{
"mcpServers": {
"regdatalab": {
"type": "streamableHttp",
"url": "https://www.regdatalab.com/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" },
"disabled": false,
"autoApprove": []
}
}
}
Set "type": "streamableHttp" explicitly. Cline defaults to the legacy SSE transport when type is missing, and an SSE GET to the endpoint returns 405. Write the key as plain text after Bearer. If the file already has other servers, add regdatalab beside them.
Or from a shell (--transport http saves "type": "streamableHttp"):
cline mcp add regdatalab https://www.regdatalab.com/mcp \
--transport http \
--header "Authorization: Bearer YOUR_API_KEY" \
--yes
The repo also has an llms-install.md that Cline can follow on its own.
stdio-only clients
Needs Node.js 18 or later:
FDA_DATA_API_KEY=YOUR_API_KEY npx -y fda-data-mcp
Keys come from regdatalab.com/signup: 50 credits on signup and 300 a month after you verify your email, no card. Configs for ChatGPT, VS Code, Codex, Windsurf and the OpenAI Responses API are in the repo: https://github.com/medley/fda-data-mcp
A real query
I asked: "Give me a manufacturing risk summary for LGM Pharma Solutions." The agent called fda_manufacturing_risk_summary (3 credits). Trimmed result, as returned on November 18, 2026:
{
"facility_footprint": { "total_count": 3 },
"inspection_summary": {
"total_inspections": 18, "nai": 8, "vai": 9, "oai": 1,
"last_inspection_date": "2025-08-06"
},
"recent_warning_letters": [{
"company_name": "LGM Pharma Solutions, LLC",
"letter_issue_date": "2026-11-02",
"subject": "CGMP/Finished Pharmaceuticals/Adulterated",
"issuing_office": "Center for Drug Evaluation and Research (CDER)",
"letter_url": "https://www.fda.gov/inspections-compliance-enforcement-and-criminal-investigations/warning-letters/lgm-pharma-solutions-llc-736085-11022026"
}],
"recent_oii_records": [{
"record_type": "483",
"publish_date": "2026-11-17",
"record_url": "https://www.fda.gov/media/196417/download"
}],
"import_risk": { "import_alert_count": 0, "import_refusal_count": 0 },
"recall_signals": { "unique_recall_count": 0 }
}
The three sites are in Irvine, CA; Rosenberg, TX; and Colorado Springs, CO. The one OAI inspection on record is from 2010. The two most recent drug quality inspections (Irvine, March 2024; Rosenberg, August 2025) were VAI, and a January 2025 bioresearch monitoring inspection at Irvine was NAI. The warning letter's first cited violation is 21 CFR 211.192, failure to thoroughly investigate out-of-specification results, here OOS assay results at stability timepoints. The Form 483 was posted to FDA's reading room on November 17, 2026.
That was one tool call. By hand, it's the Data Dashboard (inspections), the warning letter page, the reading room and the import pages, each searched separately.
Keep two caveats in any agent you build on this data (the server returns them too): no matching records does not mean a site is safe, and a 483 FDA hasn't published isn't in the public record at all.
Which to use
- Labels, adverse events, NDC or shortages only: an openFDA MCP server, or the openFDA API directly.
- Supplier qualification, audit prep, inspection or enforcement history: RegDataLab. You can run both; the tool names don't collide (
openfda_*vsfda_*).
The full openFDA vs RegDataLab comparison is at https://www.regdatalab.com/openfda-mcp. No terminal? There's a free company check, no key needed, at https://www.regdatalab.com/tools/fda-compliance-check.
Top comments (0)