Openfda Mcp Server
Query FDA drugs, devices, food enforcement, and recalls through your agent while scoping regulated health or CPG product ideas.
Overview
io.github.cyanheads/openfda-mcp-server is a MCP server for the Validate phase that queries openFDA drug, device, food, and recall datasets through your agent.
What is this MCP server?
- openFDA coverage for drugs, food, devices, and recalls via MCP tools
- STDIO and streamable-http (hosted remote plus localhost:3010/mcp pattern in schema)
- FREE OPENFDA_API_KEY from open.fda.gov raises daily limit from 1K to 120K requests
- Bun runtime hint on npm package v0.3.0
- MCP_LOG_LEVEL for observability during compliance-oriented agent workflows
- Server version 0.3.0
- Documented openFDA daily limit increase from 1K to 120K with API key
- Supports stdio and streamable-http transports per MCP schema
Community signal: 1 GitHub stars.
What problem does it solve?
Founders exploring regulated products struggle to probe FDA public data quickly, so scope decisions stall without repeatable agent access to openFDA.
Who is it for?
Solo builders validating health, med-device, or food-related ideas who need agent-driven access to official FDA open data.
Skip if: Teams needing private patient data, formal legal/regulatory sign-off only, or non-U.S. regulatory corpora.
What do I get? / Deliverables
After setup, your agent can run openFDA queries via MCP with optional API key quotas suited to iterative validation and integration prototypes.
- MCP tools backed by openFDA drug, food, device, and recall endpoints
- Configurable deployment via stdio, remote hosted MCP, or local HTTP MCP URL pattern
- Agent-ready compliance research queries with documented rate-limit uplift when keyed
Recommended MCP Servers
Journey fit
Regulated product ideas need evidence from official FDA datasets before full Build; Validate is the shelf where scope and compliance assumptions get checked. Scope subphase captures using openFDA to bound features, risks, and data sources before committing engineering time.
How it compares
openFDA public-data MCP connector, not a security pentest harness or generic LLM skill library.
Common Questions / FAQ
Who is io.github.cyanheads/openfda-mcp-server for?
Indie builders and small teams scoping regulated consumer or health products who want MCP access to FDA drugs, devices, food, and recall APIs.
When should I use io.github.cyanheads/openfda-mcp-server?
Use it during Validate scoping or Idea research—or later Build integrations—when official FDA datasets should inform features, risks, or dashboards.
How do I add io.github.cyanheads/openfda-mcp-server to my agent?
Add @cyanheads/openfda-mcp-server via npm with Bun stdio or streamable-http, set optional OPENFDA_API_KEY from open.fda.gov, and register the server in your MCP client.