Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fda Devices

NPM · @PIPEWORX/MCP-FDA-DEVICES · 2 COMPONENTS

FDA medical-device regulatory intelligence from keyless openFDA datasets.

79 Trust /100

Last scanned (23 hours ago)

Scores higher than 61% of npm servers

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fda-devices). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2520 tokens (~229/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 76% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 78

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed npm/@pipeworx/mcp-fda-devices@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-fda-devices
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-fda-devices/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3635938500
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9f9308a2c9adb59a436ade6539b5f1f7d54deb68f341b83a5c951a323d5d4effc90387e97082c849b9b11463e25179117f1f19032024c2a54c89d49f0

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~2,464 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
fda_device_510k_search ~875

Search 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/hardware -- includes cleared molecular, genomic and companion diagnostic tests. Clearance means FDA found substantial equivalence; it is not an FDA approval or endorsement. ALSO covers De Novo classification requests (K numbers beginning "DEN", e.g. DEN250057) -- these are not 510(k) clearances but a separate pathway that creates a brand-new device classification when no predicate exists; pass clearance_type:"De Novo" to find only these, or k_number for one by its DEN number. A granted De Novo shows decision "Granted" and carries the new regulation_number it created. `indication` is a BEST-EFFORT bridge, not a clinical-claim search: 510(k) records carry no indication/intended-use text at all, so it matches FDA's device CLASSIFICATION category name/definition instead (a product TYPE like "Insulin Pump", not a specific claim) and finds clearances under the matching product code(s) -- for a true clinical-indication text search (e.g. molecular/companion-diagnostic claims), use fda_device_pma_search's indication argument, which searches FDA's real approval-order narrative. Unknown arguments are rejected, not ignored. The most recent decision available lags roughly 2 weeks behind FDA's own site (openFDA's publishing cadence, not ours) -- do not treat this as same-day. `total` can exceed the 100-row `limit` cap; page further rows with `skip`.

NameTypeReqDescription
advisory_committeestring–FDA review panel name (exact), e.g. "Orthopedic" or "Microbiology".
applicantstring–Applicant/company substring.
applicant_countrystring–Applicant country, ISO 3166-1 alpha-2 code, e.g. "US" or "JP".
applicant_statestring–Applicant US state/territory code, e.g. "CA". Only populated for US applicants.
clearance_typestring–Exact pathway: Traditional, Special, Abbreviated, or Dual Track for ordinary 510(k)s; "De Novo" for a De Novo classification request/grant (DEN numbers) regardless of whether FDA processed it as "Dir…
decisionstring–Exact decision text, e.g. "Substantially Equivalent", or "Granted" for a De Novo grant.
devicestring–Device/trade name substring.
from_datestring–Earliest decision date, YYYY-MM-DD.
indicationarray–One or more device-category phrases, OR'd together, matched against FDA's device classification name/definition (device/classification.json) to find matching product code(s), then 510(k)s under those…
k_numberstring–Exact K number, e.g. K241234, or De Novo number, e.g. DEN250057.
limitnumber–Results (1-100, default 20).
product_codestring–Exact three-letter FDA product code.
skipnumber–Row offset for paging past the 100-row limit cap (openFDA `skip`, max 25000), e.g. skip=100 with limit=100 returns rows 101-200.
third_party_reviewboolean–true to keep only 510(k)s reviewed under FDA's third-party review program; false to exclude them.
to_datestring–Latest decision date, YYYY-MM-DD.
NameTypeReqDescription
clearancesarrayyes–
returnednumberyes–
sourcestringyes–
totalnumberyes–

No examples provided.

fda_device_510k_summary ~117

Get 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 clearances were never digitized; that returns summary_available:false with a reason, not an error.

NameTypeReqDescription
k_numberstringyesExact K number, e.g. K253470.
NameTypeReqDescription
detail_pagestringyes–
k_numberstringyes–
reasonstring––
reviewobject––
review_availablebooleanyes–
sourcestringyes–
summaryobject––
summary_availablebooleanyes–

No examples provided.

fda_device_adverse_events ~162

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.

NameTypeReqDescription
application_numberstring–PMA or 510(k) number.
devicestring–Brand or generic device name.
event_typestring–Death, Injury, Malfunction, or Other.
from_datestring–Earliest FDA receive date, YYYY-MM-DD.
limitnumber–Results (1-50, default 10).
manufacturerstring–Manufacturer name.
product_codestring–Exact product code.
NameTypeReqDescription
reportsarrayyes–
returnednumberyes–
sourcestringyes–
totalnumberyes–

No examples provided.

fda_device_classification ~85

Look 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.

NameTypeReqDescription
devicestring––
limitnumber–Rows (1-100, default 20).
product_codestring––
regulation_numberstring––
NameTypeReqDescription
classificationsarrayyes–
returnednumberyes–
sourcestringyes–
totalnumberyes–

No examples provided.

fda_device_company_profile ~84

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.

NameTypeReqDescription
companystringyesCompany/manufacturer name.
limit_per_datasetnumber–Rows per dataset (1-20, default 5).
NameTypeReqDescription
clearances_510kobjectyes–
companystringyes–
interpretationstringyes–
maude_reportsobjectyes–
pma_decisionsobjectyes–
recallsobjectyes–

No examples provided.

fda_device_establishment_search ~86

Search 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.

NameTypeReqDescription
firmstring––
limitnumber––
listing_numberstring––
product_codestring––
registration_numberstring––
NameTypeReqDescription
establishmentsarrayyes–
returnednumberyes–
sourcestringyes–
totalnumberyes–

No examples provided.

fda_device_event_counts ~155

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.

NameTypeReqDescription
count_fieldstringyesWhat to rank by. For "which DEVICES had the most reports" use device.generic_name.exact (device type) or device.brand_name.exact (specific product).
limitnumber–Buckets (1-100, default 20).
querystring–Optional raw openFDA MAUDE filter, e.g. 'date_received:[20250101+TO+20261231]'. Omit to rank across all reports.
NameTypeReqDescription
bucketsarrayyes–
returnednumberyes–
sourcestringyes–
totalnumberyes–

No examples provided.

fda_device_pma_search ~575

Search 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 companion diagnostics and molecular residual disease (MRD) / ctDNA monitoring tests (e.g. Signatera, Guardant360 CDx) -- these are FDA-approved tests, not cleared devices, so this tool (not 510(k)) is the one that finds them. `indication` matches free text in FDA's own published approval-order narrative (`ao_statement`) -- the intended-use/indication language FDA wrote when it approved the device -- so a caller who describes what a test DOES or what condition/biomarker it monitors (without knowing any brand name) can still find it; `device` only matches the trade/generic NAME field and returns nothing for a condition-only question. Supplements may represent manufacturing or labeling changes rather than new devices, so a supplement's own ao_statement can be a narrow procedural note (e.g. "approval of a post-approval study protocol") rather than the full clinical indication -- pass several synonymous indication phrases (FDA's exact wording varies by product and rarely matches a lay term) rather than one exact phrase.

NameTypeReqDescription
applicantstring–Applicant/company substring.
devicestring–Trade or generic device name substring.
from_datestring–Earliest decision date, YYYY-MM-DD.
indicationarray–One or more clinical indication / intended-use / condition phrases, OR'd together, matched as exact phrases against the FDA approval-order narrative text (ao_statement) -- NOT the device name. Use th…
limitnumber–Results (1-100, default 20).
pma_numberstring–Exact PMA number, optionally including supplement suffix.
product_codestring–Exact FDA product code.
to_datestring–Latest decision date, YYYY-MM-DD.
NameTypeReqDescription
approvalsarrayyes–
returnednumberyes–
sourcestringyes–
totalnumberyes–

No examples provided.

fda_device_product_code_profile ~76

Build 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.

NameTypeReqDescription
limit_per_datasetnumber––
product_codestringyes–
NameTypeReqDescription
classificationsobjectyes–
clearances_510kobjectyes–
interpretationstringyes–
maude_reportsobjectyes–
pma_decisionsobjectyes–
product_codestringyes–
recallsobjectyes–

No examples provided.

fda_device_recalls ~147

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.

NameTypeReqDescription
firmstring–Recalling firm substring.
from_datestring–Earliest posted date, YYYY-MM-DD.
k_numberstring–Exact related K number.
limitnumber–Results (1-100, default 20).
product_codestring–Exact FDA product code.
querystring–Product or reason text.
statusstring–Recall status, e.g. Ongoing or Terminated.
NameTypeReqDescription
recallsarrayyes–
returnednumberyes–
sourcestringyes–
totalnumberyes–

No examples provided.

fda_device_udi_search ~102

Search 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.

NameTypeReqDescription
companystring––
limitnumber––
primary_distring––
product_codestring––
querystring–Brand or device description.
NameTypeReqDescription
devicesarrayyes–
returnednumberyes–
sourcestringyes–
totalnumberyes–

No examples provided.

Install

How do I install the Fda Devices MCP server?

Fda Devices runs locally as an npm package, launched with npx -y @pipeworx/mcp-fda-devices. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-fda-devices

# add to Claude Code
claude mcp add pipeworx-io-fda-devices -- npx -y @pipeworx/mcp-fda-devices
Common questions

What is the Fda Devices MCP server?

Fda Devices is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fda-devices. FDA medical-device regulatory intelligence from keyless openFDA datasets. This page covers its npm package (@pipeworx/mcp-fda-devices).

Is the Fda Devices MCP server safe to use?

Fda Devices scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Fda Devices MCP server expose?

Fda Devices exposes 11 tools: fda_device_510k_search, fda_device_510k_summary, fda_device_pma_search, fda_device_recalls, fda_device_adverse_events, and 6 more. Their descriptions and schemas cost roughly 2,464 tokens of context every time the server is loaded.

Is the Fda Devices MCP server still maintained?

Fda Devices is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Fda Devices MCP server under?

Fda Devices declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.