openFDA Regulatory Metadata
Resolve FDA application numbers and product names to regulatory metadata (CDER, CBER, CDRH).
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
openfda-mcpclaude mcp add openfda-regulatory-metadata -- uvx openfda-mcp==0.1.0
{
"mcpServers": {
"openfda-regulatory-metadata": {
"command": "uvx",
"args": [
"openfda-mcp==0.1.0"
]
}
}
}
Frequently asked questions
What is openFDA Regulatory Metadata?
Resolve FDA application numbers and product names to regulatory metadata (CDER, CBER, CDRH).
How do I install openFDA Regulatory Metadata?
It runs on your machine. In Claude Code: claude mcp add openfda-regulatory-metadata -- uvx openfda-mcp==0.1.0. For other clients, paste the JSON configuration from this page into their MCP settings.
Does openFDA Regulatory Metadata need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is openFDA Regulatory Metadata open source?
Its code is public on GitHub, but the repository does not declare a standard license.
Who maintains openFDA Regulatory Metadata?
It is published by Black-Swan-Causal-Labs. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.