Skip to content

deviCERTS medical device regulatory data MCP server

com.devicerts/medical-devicesdevicerts.comstreamable-httpv1.2.0Scanned

FDA 510(k)/PMA/De Novo, GUDID, recall and EUDAMED device and certificate data. Read-only, no login.

15 tools: 15 only read.

Tools: 0 delete, 0 irreversible, 0 write, 15 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the deviCERTS medical device regulatory data MCP server can do

The deviCERTS medical device regulatory data MCP server is published by devicerts.com, a domain the MCP Registry verified. It has 15 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

3 tools bring in text other people can write (get_device_certificates, search and fetch).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Only reads 15Show 15 read-only tools
  • fetchFetch one record in the standard search/fetch connector format: the device or manufacturer behind a search id (device:<slug> or manufacturer:<slug>) as Markdown text, with its url …Reads text others writeNo findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Fetch one record in the standard search/fetch connector format: the device or manufacturer behind a search id (device:<slug> or manufacturer:<slug>) as Markdown text, with its url and metadata (retrieval date, reuse terms). Use when the client works only with the standard search and fetch pair (ChatGPT connectors and deep research). Do not use when get_device or get_manufacturer is available: they return structured fields and a detail level. Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Fetch a record (ChatGPT format)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • find_device_by_identifierLook up devices by one exact regulatory identifier: FDA 510(k), PMA or De Novo number, UDI-DI (GS1 or HIBCC) or EU Basic UDI-DI.No findings

    Why it is in this group

    • The name "find_device_by_identifier" says "find": a word for reading.
    Description, as the server wrote it
    Look up devices by one exact regulatory identifier: FDA 510(k), PMA or De Novo number, UDI-DI (GS1 or HIBCC) or EU Basic UDI-DI. Returns exact_matches (the identifier is the device's primary reference or UDI-DI) and related devices that carry it in another field (a Basic UDI-DI or a submission number often covers several models). Use when the question contains an identifier such as K110287 or a GTIN. Do not use for names or free text (use search_devices) or when the slug is already known (use get_device). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Find a device by identifier
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_data_sourcesDescribe the registries DevicErts compiles (EUDAMED, FDA GUDID, 510(k), De Novo, PMA, recalls, establishment registrations): region, record count, last sync date, sync cadence and …No findings

    Why it is in this group

    • The name "get_data_sources" says "get": a word for reading.
    Description, as the server wrote it
    Describe the registries DevicErts compiles (EUDAMED, FDA GUDID, 510(k), De Novo, PMA, recalls, establishment registrations): region, record count, last sync date, sync cadence and reuse terms of each, plus the catalogue totals. Takes no arguments. Use when the question is how current or complete the data are, or under which terms they may be reused. Do not use for facts about a device or a company (use search_devices or search_manufacturers). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Data sources and freshness
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_deviceGet the DevicErts record of one device by slug.No findings

    Why it is in this group

    • The name "get_device" says "get": a word for reading.
    Description, as the server wrote it
    Get the DevicErts record of one device by slug. summary (default): names, manufacturer, status, risk class with its legal system, and every authorization or listing with number, dates and status. detail=full adds identifiers (UDI-DI, Basic UDI-DI, catalogue numbers), FDA product codes, EMDN/GMDN codes, EU certificates, FDA recalls, EU market availability and registry properties. Old slugs resolve to the current one. Use when the slug is known and the device's facts are needed. Prefer this over `fetch`. Do not use to find a device (use search_devices or find_device_by_identifier) or when only recalls or only certificates are needed (use get_device_recalls or get_device_certificates, smaller answers). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Get a device record
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_device_certificatesList the EU notified-body certificates (from EUDAMED) of one device by slug: certificate number, type, legislation (MDR, IVDR, MDD, IVDD, AIMDD), notified body, issue and expiry da…Reads text others writeNo findings

    Why it is in this group

    • The name "get_device_certificates" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    List the EU notified-body certificates (from EUDAMED) of one device by slug: certificate number, type, legislation (MDR, IVDR, MDD, IVDD, AIMDD), notified body, issue and expiry dates, status (such as issued, supplemented, suspended, withdrawn) and whether EUDAMED still lists it. Use when the question is about CE certificates, notified bodies or certificate expiry of a known device. Do not use for FDA clearances or approvals (they are authorizations in get_device), for certificates by number, notified body or manufacturer (use search_certificates) or to find the device (use search_devices). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Get the EU certificates of a device
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_device_recallsList the U.S.No findings

    Why it is in this group

    • The name "get_device_recalls" says "get": a word for reading.
    Description, as the server wrote it
    List the U.S. FDA recalls linked to one device by slug: recall number, FDA recall class (I, II or III), status (ongoing, completed or terminated), start date, reason, and whether the recall names this device or only its shared 510(k) or PMA submission. Optional status filter; newest first, at most 100. Use when the question is about recalls or field safety actions of a known device. Do not use for recalls across devices, by product, firm or date (use search_recalls), for the whole record (use get_device with detail=full) or to find the device (use search_devices). EU devices without an FDA record have no recall data. Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Get the recalls of a device
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_manufacturerGet the DevicErts record of one manufacturer by slug: name and registered names, country with its basis, registry identifiers (EUDAMED SRN, FDA FEI, DUNS), device counts per regist…No findings

    Why it is in this group

    • The name "get_manufacturer" says "get": a word for reading.
    Description, as the server wrote it
    Get the DevicErts record of one manufacturer by slug: name and registered names, country with its basis, registry identifiers (EUDAMED SRN, FDA FEI, DUNS), device counts per registry and risk class, up to 10 of its devices, its EU certificates and up to 10 recent FDA recalls matched to it. Use when the manufacturer slug is known (from search_manufacturers or get_device) and the company profile is needed. Do not use to find a company by name (use search_manufacturers), to list all its devices (use search_devices with the manufacturer filter), or for all its recalls or certificates (use search_recalls with firm, search_certificates with manufacturer). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Get a manufacturer
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_recallGet one U.S.No findings

    Why it is in this group

    • The name "get_recall" says "get": a word for reading.
    Description, as the server wrote it
    Get one U.S. FDA device recall by its recall number: status (ongoing, completed or terminated), FDA recall class, start date, reason, product description, product code, recalling firm, the 510(k), PMA or De Novo numbers it names and the name-matched DevicErts manufacturer page. Use when a recall number is known, such as Z-0079-2022. Do not use to find recalls by product, firm, class or date (use search_recalls) or for the recalls of one device (use get_device_recalls). EU field safety notices (FSCA) are not in the catalogue. Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Get an FDA recall by number
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_certificatesSearch EU notified-body certificates (EUDAMED) by certificate number, notified body number or name, holder name or SRN, legislation (MDR, IVDR), status and validity date, with offs…No findings

    Why it is in this group

    • The name "search_certificates" says "search": a word for reading.
    Description, as the server wrote it
    Search EU notified-body certificates (EUDAMED) by certificate number, notified body number or name, holder name or SRN, legislation (MDR, IVDR), status and validity date, with offset paging. Returns up to 20 certificates per page: number, type, legislation, status, issue and expiry dates, notified body and holder with their DevicErts pages, plus total and next_offset. Use when a certificate number is known, or the question is which certificates a notified body issued or a manufacturer holds. Do not use for the certificates of one known device (use get_device_certificates) or for FDA clearances (use find_device_by_identifier). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Search EU certificates
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_devicesSearch the DevicErts medical device catalogue by text, with filters for registry, region, risk class and manufacturer, and offset paging.No findings

    Why it is in this group

    • The name "search_devices" says "search": a word for reading.
    Description, as the server wrote it
    Search the DevicErts medical device catalogue by text, with filters for registry, region, risk class and manufacturer, and offset paging. Returns up to 20 devices per page (slug, page URL, manufacturer, risk class, registries, status, primary reference, UDI-DI), the total, next_offset and more_results_url. Use when a device is described by name, type, model or company, or a filtered list is needed. Prefer this over `search`. Do not use for an exact 510(k), PMA, De Novo number or UDI-DI (use find_device_by_identifier) or for companies (use search_manufacturers). Pass a slug to get_device for the full record. Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Search medical devices
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_establishmentsSearch registered establishments: EU economic operators and authorities in EUDAMED (manufacturers, authorised representatives, importers, notified bodies, competent authorities, sp…No findings

    Why it is in this group

    • The name "search_establishments" says "search": a word for reading.
    Description, as the server wrote it
    Search registered establishments: EU economic operators and authorities in EUDAMED (manufacturers, authorised representatives, importers, notified bodies, competent authorities, sponsors) by name or SRN with role and country filters and offset paging, or one FDA establishment registration by FEI number (a single hit, no paging). Returns up to 20 hits per page (registry, identifier and its type, name, role, country, status, page URL) and next_offset. Use when the question is about a registration identifier (SRN or FEI) or an operator role such as authorised representative. Do not use to find a company profile by name (use search_manufacturers) or its devices (use search_devices). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Search establishments and operators
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_gudid_listingsList FDA GUDID listings, one row per listing with its primary UDI-DI, brand or device name, version or model, labeler, risk class and commercial status; records without a primary D…No findings

    Why it is in this group

    • The name "search_gudid_listings" says "search": a word for reading.
    Description, as the server wrote it
    List FDA GUDID listings, one row per listing with its primary UDI-DI, brand or device name, version or model, labeler, risk class and commercial status; records without a primary DI are left out. A query that is a GTIN or HIBCC code is matched to the primary DI first (exact_match true). Optional labeler filter, offset paging, up to 20 rows per page. Use when the question is about GUDID listings or a UDI-DI in the U.S. market, e.g. all listings of a brand. Do not use for a full device record (use get_device), a 510(k), PMA or De Novo number or EU identifiers (use find_device_by_identifier), or devices across all registries (use search_devices). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Search FDA GUDID device listings
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_manufacturersSearch medical device manufacturers by company name, optionally in one country, with offset paging.No findings

    Why it is in this group

    • The name "search_manufacturers" says "search": a word for reading.
    Description, as the server wrote it
    Search medical device manufacturers by company name, optionally in one country, with offset paging. Returns up to 20 companies per page with slug, page URL and country, the total and next_offset. Use when a company is named or looked for. Do not use to find devices (use search_devices, which also filters by manufacturer name). Pass a slug to get_manufacturer for the company record. Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Search manufacturers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_recallsSearch U.S.No findings

    Why it is in this group

    • The name "search_recalls" says "search": a word for reading.
    Description, as the server wrote it
    Search U.S. FDA medical device recalls across all devices by words (product description, recall reason, recalling firm or recall number), product code, firm, submission number or pathway, start-date range, recall class and status, with offset paging. Returns up to 20 recalls per page, newest first: recall number, class, status, start date, reason, product code, firm, submissions and the name-matched DevicErts manufacturer page, plus total and next_offset. Use when the question covers recalls in general or all recalls of a company, e.g. ongoing Class I recalls of a product code. Do not use for the recalls of one known device (use get_device_recalls) or for EU data (recalls are FDA only). Read-only, no login. Data: public EUDAMED and U.S. FDA records, synced monthly, EU certificates weekly (dates in get_data_sources). Cached up to 1 hour; limit 300 calls a minute per IP.

    Annotations the server declares

    • title: Search FDA recalls
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:19 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools3 added.+3 addedView diff
  2. Tools4 added, 8 changed.+4 added~8 changedView diff

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http medical-devices https://devicerts.com/mcp
claude mcp add --transport http medical-devices https://devicerts.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__medical-devices__search_devices",
      "mcp__medical-devices__find_device_by_identifier",
      "mcp__medical-devices__get_device",
      "mcp__medical-devices__get_device_recalls",
      "mcp__medical-devices__get_device_certificates",
      "mcp__medical-devices__search_recalls",
      "mcp__medical-devices__search_certificates",
      "mcp__medical-devices__search_manufacturers",
      "mcp__medical-devices__get_manufacturer",
      "mcp__medical-devices__get_data_sources",
      "mcp__medical-devices__search_gudid_listings",
      "mcp__medical-devices__get_recall",
      "mcp__medical-devices__search_establishments",
      "mcp__medical-devices__search",
      "mcp__medical-devices__fetch"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as medical-devices. Review it before you use it.

Capability tags behind 3 rules
  • mcp__medical-devices__get_device_certificates untrusted-input
  • mcp__medical-devices__search untrusted-input
  • mcp__medical-devices__fetch untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.devicerts/medical-devices/verify?hash=4b684dac3d1371bd1e4d5a6301035cd900c6a601acaa90600ee0c0d188125e93" | jq -e '.changed == false'

Pinned hash 4b684dac3d13, from Nov 18, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.devicerts/medical-devices/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.devicerts/medical-devices
[![Anlyon Radar](https://radar.anlyon.com/badge/com.devicerts/medical-devices.svg)](https://radar.anlyon.com/servers/com.devicerts/medical-devices)

Source: MCP Registry · repository. Synced Nov 18, 2026, 14:17 UTC.

deviCERTS medical device regulatory data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the deviCERTS medical device regulatory data MCP server safe?

No scan can promise that. What its definitions show: 15 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the deviCERTS medical device regulatory data MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the deviCERTS medical device regulatory data MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the deviCERTS medical device regulatory data MCP server have?

15 tools: 15 read. search_devices, find_device_by_identifier, get_device, get_device_recalls, get_device_certificates, search_recalls, search_certificates, search_manufacturers and 7 more.

Does the deviCERTS medical device regulatory data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the deviCERTS medical device regulatory data MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the deviCERTS medical device regulatory data MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.