protogrid

Search / io.github.pipeworx-io/fda-devices

Fda Devices

R0· no sign-in

FDA medical-device regulatory intelligence from keyless openFDA datasets.

v0.1.7 · active · repository · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality–not scored
Trust97of 100
Uptime, 30 days97%
Latency p5049 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "fda-devices": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/fda-devices/mcp"
    }
  }
}
claude mcp add --transport http fda-devices https://gateway.pipeworx.io/fda-devices/mcp
[mcp_servers.fda-devices]
url = "https://gateway.pipeworx.io/fda-devices/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fda-devices": {
      "type": "remote",
      "url": "https://gateway.pipeworx.io/fda-devices/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "fda-devices": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/fda-devices/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=fda-devices&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZ2F0ZXdheS5waXBld29yeC5pby9mZGEtZGV2aWNlcy9tY3AifQ%3D%3D"
}
{
  "servers": {
    "fda-devices": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/fda-devices/mcp"
    }
  }
}
{
  "mcpServers": {
    "fda-devices": {
      "httpUrl": "https://gateway.pipeworx.io/fda-devices/mcp"
    }
  }
}
extensions:
  "fda-devices":
    enabled: true
    name: "fda-devices"
    type: streamable_http
    uri: "https://gateway.pipeworx.io/fda-devices/mcp"
    timeout: 300

Quality – / 100not scored

Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygienen/a · weight 30
  • n/a
    tools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool list unknown
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

Tool list unknown · tools last changed 2026-10-20 · checked 2026-10-20 12:13 UTC

Tool changes

  • fda_device_product_code_profileremoved

    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.

  • fda_device_establishment_searchremoved

    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.

  • fda_device_udi_searchremoved

    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.

  • fda_device_classificationremoved

    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.

  • fda_device_company_profileremoved

    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.

  • fda_device_adverse_eventsremoved

    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_recallsremoved

    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_pma_searchremoved

    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.

  • fda_device_510k_summaryremoved

    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.

  • fda_device_510k_searchremoved

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

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 97 / 100

provenance90
liveness99
freshness100
hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-97% +updated-24d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://gateway.pipeworx.io/fda-devices/mcp streamable-httpnoneyes97%49 ms2025-03-262026-10-20

Tools (0)

No tools observed. Tools appear once a credential-free probe can list them.

Schemas: list_tools.

Similar MCP servers

More from io.github.pipeworx-io

And 1,855 more from this publisher.

Official server.json
{
  "name": "io.github.pipeworx-io/fda-devices",
  "title": "Fda Devices",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://gateway.pipeworx.io/fda-devices/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.7",
  "repository": {
    "url": "https://github.com/pipeworx-io/mcp-fda-devices",
    "source": "github"
  },
  "websiteUrl": "https://pipeworx.io/packs/fda-devices",
  "description": "FDA medical-device regulatory intelligence from keyless openFDA datasets."
}