OpenFDA Regulatory Metadata vs Mdr Medical Device MCP
A side-by-side look at the OpenFDA Regulatory Metadata and Mdr Medical Device MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OpenFDA Regulatory Metadata for biology & bioinformatics work as a local process; choose Mdr Medical Device MCP for biology & bioinformatics as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose OpenFDA Regulatory Metadata when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENFDA_API_KEY. - You want tools like
search_drug_label, lookup_drugsfda_application, resolve_drug_to_application.
Choose Mdr Medical Device MCP when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 56/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | OPENFDA_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View OpenFDA Regulatory Metadata | View Mdr Medical Device MCP |
Tools & capabilities
OpenFDA Regulatory Metadata tools 7
search_drug_labelSearch openFDA drug labels (SPL) for a term.lookup_drugsfda_applicationFetch Drugs@FDA application metadata for an NDA/BLA/ANDA number.resolve_drug_to_applicationResolve a brand or generic drug name to its NDA/BLA application number(s). Bridges drug-name-only sources (registry inventories, product lists) to FDA regulatory metadata. Searches the brand and generic name fields directly rather than label prose, so another product merely *mentioning* this drug does not produce a false match.screen_for_rwe_signalsEXPERIMENTAL. Sweep drug labels for registry / real-world-evidence signals. Searches the label corpus for terms suggesting registry, natural-history or other real-world evidence, then aggregates hits by application number with snippets showing where each term matched. **This tool is unvalidated and has a known false-positive problem.** It has no ground-truth oracle, and below the strongest hits the results are dominated by applications whose labels use "registry" in an unrelated sense. Its output is a candidate list for human review — not a finding, and not a count you should report.lookup_device_submissionLook up a CDRH device submission by its number. Handles all four device pathways: 510(k) K-numbers ("K203571"), De Novo grants ("DEN160026" — stored in the 510(k) endpoint, not a separate one), PMA P-numbers ("P230044"), and HDE H-numbers. Supplement suffixes ("P230044/S001") are stripped before lookup.classify_device_product_codeResolve a CDRH product code to its device class and medical specialty.validate_device_applicationValidate a device number and derive class, specialty and category in one call. Chains lookup_device_submission -> classify_device_product_code, which is the full three-hop resolution: number -> product_code -> classification.
Mdr Medical Device MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
OpenFDA Regulatory Metadata
{
"mcpServers": {
"openfda-regulatory-metadata": {
"command": "uvx",
"args": [
"openfda-mcp"
],
"env": {
"OPENFDA_API_KEY": "YOUR_OPENFDA_API_KEY_HERE"
}
}
}
}
Mdr Medical Device MCP
{
"mcpServers": {
"mdr-medical-device-mcp": {
"command": "uvx",
"args": [
"mdr-medical-device-mcp"
]
}
}
}
Frequently asked questions
OpenFDA Regulatory Metadata is categorized under Biology & Bioinformatics and uses a local stdio subprocess. Mdr Medical Device MCP belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick OpenFDA Regulatory Metadata for biology & bioinformatics work and Mdr Medical Device MCP for biology & bioinformatics.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
OpenFDA Regulatory Metadata is listed as free. Mdr Medical Device MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openfda-regulatory-metadata and mdr-medical-device-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, OpenFDA Regulatory Metadata has a quality signal of 56/100 (Good) with 6 views, 0 installs and 0 GitHub stars. Mdr Medical Device MCP has 40/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.