Health · Local MCP server
openFDA Regulatory Metadata
Resolve FDA application numbers and product names to regulatory metadata (CDER, CBER, CDRH).
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.blackswancausallabs/openfda-mcp- Version
- 0.1.0
- Status
- Active
- Category
- health
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-08-07
- Updated
- 2026-08-07
- Publisher
- com.blackswancausallabs · 4 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain blackswancausallabs.com · how
- Repository
- github.com/Black-Swan-Causal-Labs/openfda-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | openfda-mcp | 0.1.0 | stdio |
How to connect openFDA Regulatory Metadata
openFDA Regulatory Metadata runs locally from a Python package published to PyPI: openfda-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx openfda-mcp.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"openfda-mcp": {
"command": "uvx",
"args": [
"openfda-mcp"
]
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.blackswancausallabs
| Server | Runs |
|---|---|
| DAG Studio MCPCausal DAG analysis: backdoor paths, adjustment sets, bias simulation. Validated against dagitty. | Remote · HTTPLive check: sign-in required |
| ROBINS-I V2 MCPROBINS-I V2 (not V1): risk of bias in one result of a non-randomized cohort study. | Local · stdio |
| TARGET Checklist MCPScore how completely a target-trial-emulation study reports what the TARGET guideline requires. | Local · stdio |
More health servers
| Server | Runs |
|---|---|
| OOTWOracle - Psychedelic Medicine IntelligenceAI predictions on psychedelic medicine regulation. 8-agent swarm, 460+ daily signals, free API. | Remote · HTTPLive check: ✗ no handshake |
| OpenfdaFDA drug data via openFDA: adverse-event reports and safety-signal tools (FAERS search, event… | Remote · HTTPLive check: ✓ handshake |
| Openfda MCPFDA open data: drug recalls, adverse events, and approved drugs. | Local · stdio |
| Openfda MCP ServerQuery FDA data on drugs, food, devices, and recalls via openFDA. STDIO or Streamable HTTP. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| OpenFDA Safety DataSearch FDA safety data: drug adverse events, recalls, and device events. | Remote · HTTPLive check: sign-in required |
| OpentargetsOpen Targets MCP server for targets, diseases, drugs, variants, and evidence. | Local · stdio |
| OpentargetsOpen Targets MCP - disease/target/drug knowledge graph. | Remote · HTTPLive check: ✓ handshake |
| Opentargets MCPKeyless MCP server for Open Targets: gene/disease/drug search, target details, disease associations. | Local · stdio |