fda-devices 6 tools

MCP server exposing 6 tools for fda-devices.

Endpoint

This URL is a JSON-RPC 2.0 endpoint over HTTP. Issue POST requests with a JSON-RPC body. Browsers and search crawlers land here on GET.

POST https://gateway.pipeworx.io/fda-devices/mcp
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"tools/list"}

Tools

• fda_device_510k_search — Search FDA 510(k) premarket notifications by device, applicant, product code, or K number. Clearance means FDA found substantial equivalence; it is not an FDA approval or endorsement.
• fda_device_pma_search — Search FDA Premarket Approval (PMA) decisions and supplements by trade/generic name, applicant, product code, or PMA number. Supplements may represent manufacturing or labeling changes rather than new devices.
• fda_device_recalls — Search 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_events — Search 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_counts — Aggregate 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_profile — Build 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.

Full documentation

Code samples (curl / TypeScript / one-click client install), schemas, and the live playground are on the pack page:
https://pipeworx.io/packs/fda-devices/

About Pipeworx

Pipeworx is an open MCP gateway connecting AI agents to live data. pipeworx.io