FDA Approvals vs Fda Devices
A side-by-side look at the FDA Approvals and Fda Devices MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose FDA Approvals for biology & bioinformatics work over a hosted endpoint; choose Fda Devices 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 FDA Approvals when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
fda_drug_approval_search, fda_drug_label, fda_recall_search.
Choose Fda Devices when
- You need dedicated capabilities in the Biology & Bioinformatics domain.
- You prefer a local stdio subprocess transport.
- You want tools like
fda_device_510k_search, fda_device_510k_summary, fda_device_pma_search.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Biology & Bioinformatics | Biology & Bioinformatics |
| Quality signal | 43/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | 11 |
| Full listing | View FDA Approvals | View Fda Devices |
Tools & capabilities
FDA Approvals tools 6
fda_drug_approval_searchSearch FDA drug approvals from Drugs@FDA filtered by sponsor, brand name, generic, or approval date.fda_drug_labelFDA-approved drug label for a brand/generic — indications, dosage, contraindications, warnings.fda_recall_searchSearch drug/device/food recall events by Class I/II/III and date.fda_adverse_eventsAggregate FAERS adverse-event reports — total, unique reactions, top reactions (deduped by safetyreportid).fda_510k_searchSearch FDA 510(k) medical-device clearances.fda_drug_shortagesCurrent FDA-tracked drug-shortage list.
Fda Devices tools 11
fda_device_510k_searchSearch FDA 510(k) premarket notifications by device, applicant, product code, K number, review panel, clearance type, decision, applicant location, third-party review status, or device-category text (via `indication`). Covers IN VITRO DIAGNOSTIC (IVD) tests and diagnostic devices, not just implants…fda_device_510k_summaryGet the FDA 510(k) summary/statement document and FDA review (decision memo) for one clearance, by K number — the actual filing, not just the "a document exists" flag from fda_device_510k_search. Shows the predicate device claimed and the testing behind the equivalence finding. Older/paper-only cle…fda_device_pma_searchSearch FDA Premarket Approval (PMA) decisions and supplements by trade/generic name, applicant, product code, PMA number, or CLINICAL INDICATION/condition text (via `indication`). Which diagnostic tests are FDA-approved: covers high-risk IN VITRO DIAGNOSTIC (IVD) tests approved via PMA, including c…fda_device_recallsSearch FDA medical-device recall records by firm, product, product code, K number, status, or date. A recall record describes a correction/removal action and does not by itself establish patient harm.fda_device_adverse_eventsSearch FDA MAUDE medical-device reports by manufacturer, brand/device, product code, event type, or PMA/510(k) number. MAUDE reports are unverified signals: they cannot establish causation, incidence, prevalence, or comparative safety.fda_device_event_countsAggregate MAUDE reports for a device query by event type, manufacturer, product code, or receive date. Counts reflect reporting and database artifacts—not event rates or causal risk—and must not be compared without exposure denominators.fda_device_company_profileBuild a bounded FDA regulatory snapshot for one device company across 510(k), PMA, recalls, and MAUDE. Dataset name matching is imperfect and MAUDE counts are signals, not safety rates.fda_device_classificationLook up FDA device classification and regulatory context by product code, device name, or regulation number. Classification describes the product-code category, not a specific product’s clearance or approval.fda_device_udi_searchSearch FDA GUDID/UDI records by brand, company, device identifier, or product code. A UDI record describes an identified device in GUDID; it does not establish current sales, availability, clearance, approval, or safety.fda_device_establishment_searchSearch FDA device registration/listing data by firm, registration number, product code, or listing number. Registration/listing does not mean FDA approval, clearance, certification, or endorsement.fda_device_product_code_profileBuild a bounded cross-dataset snapshot for one FDA product code: classification, recent 510(k)s, PMAs, recalls, and MAUDE reports. Dataset counts have different meanings; MAUDE counts are not event rates.
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.
FDA Approvals
{
"mcpServers": {
"fda-approvals": {
"url": "https://fda-approvals-mcp.atlasword.workers.dev/mcp"
}
}
}
Fda Devices
{
"mcpServers": {
"fda-devices": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-fda-devices"
]
}
}
}
Frequently asked questions
FDA Approvals is categorized under Biology & Bioinformatics and uses a remote HTTP/SSE transport. Fda Devices belongs to Biology & Bioinformatics and uses a local stdio subprocess. Pick FDA Approvals for biology & bioinformatics work and Fda Devices 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.
FDA Approvals has no declared pricing — check the project's own site. Fda Devices 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 fda-approvals and fda-devices as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, FDA Approvals has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Fda Devices has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.