_ registry / mcp http-sse · checked 21m ago

com.devicerts/medical-devices

https://devicerts.com

Registry code: 8d44a396dc9236b7

api record

DevicErts (devicerts.com) is a catalogue of medical devices compiled from public registries: EUDAMED (European Union) and the U.S. FDA (510(k), De Novo, PMA, GUDID, recalls, establishment registrations). Every result carries the canonical DevicErts page URL, a citation line and the reuse terms of each source. Informational only, not medical or regulatory advice. DevicErts is not an official register and is not affiliated with the U.S. FDA or the European Commission. Statuses are as of the stated date; the record in the source registry prevails.

endpoint
https://devicerts.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is com.devicerts/medical-devices live?
Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
Is com.devicerts/medical-devices free to use?
Yes — the hub reached it with no key and no payment.
What tools does com.devicerts/medical-devices have?
8 tools: get_manufacturer, search_devices, get_device, search_manufacturers, search, fetch, find_device_by_identifier, get_data_sources.
Is com.devicerts/medical-devices safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
290ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_data_sources open 21m ago

    The registries DevicErts compiles (EUDAMED, FDA GUDID, 510(k), De Novo, PMA, recalls, establishment registrations): region, number of records in the catalogue, last sync date, sync cadence and reuse terms of each, plus the catalogue totals.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_manufacturer unknown never probed

    The DevicErts record of one manufacturer: 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, EU certificates and recent FDA recalls matched to it.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 240,
          "minLength": 1,
          "description": "The manufacturer slug, the last part of its https://devicerts.com/manufacturers/<slug> URL."
        }
      }
    }
    arguments 15 lines
  • search_devices unknown never probed

    Full-text search of the DevicErts catalogue (EUDAMED, FDA 510(k), De Novo, PMA, GUDID). Returns up to 20 devices, each with its page URL, manufacturer, risk class, registries, headline status, primary reference and UDI-DI. Results are a first page only; more_results_url opens the same search on the website.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Number of results, 1 to 20. Default 10."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Search text: device or trade name, model or catalogue number, manufacturer name, or an identifier."
        },
        "registry": {
          "enum": [
            "eudamed",
            "fda_510k",
            "fda_pma",
            "fda_udi"
          ],
          "type": "string",
          "description": "Only devices listed in this registry: eudamed, fda_510k (510(k) and De Novo), fda_pma or fda_udi (GUDID)."
        },
        "device_class": {
          "enum": [
            "Class I",
            "Class II",
            "Class IIa",
            "Class IIb",
            "Class III",
            "Class A",
            "Class B",
            "Class C",
            "Class D"
          ],
          "type": "string",
          "description": "Only devices of this risk class (EU MDR I/IIa/IIb/III, US FDA I/II/III, EU IVDR A-D)."
        },
        "manufacturer": {
          "type": "string",
          "maxLength": 100,
          "minLength": 2,
          "description": "Only devices of manufacturers whose name contains these words."
        }
      }
    }
    arguments 52 lines
  • get_device unknown never probed

    The DevicErts record of one device: names as registered, manufacturer, headline status, risk class with its legal system, and every authorization, registration and listing with number, dates and status. detail=full adds identifiers (UDI-DI, Basic UDI-DI, catalogue and submission numbers), FDA product codes, EMDN and GMDN codes, EU notified-body certificates, FDA recalls, EU market availability and the registry properties. Renamed or merged pages resolve to the current slug.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "maxLength": 240,
          "minLength": 1,
          "description": "The device slug, the last part of its https://devicerts.com/devices/<slug> URL (a full page URL is accepted too)."
        },
        "detail": {
          "enum": [
            "summary",
            "full"
          ],
          "type": "string",
          "description": "summary (default): names, manufacturer, status, class, authorizations. full: adds identifiers, nomenclature codes, EU certificates, recalls, EU market availability and registry properties."
        }
      }
    }
    arguments 23 lines
  • search_manufacturers unknown never probed

    Search medical device manufacturers by name. Returns up to 20 companies with their DevicErts page URL, slug and country.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Number of results, 1 to 20. Default 10."
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "minLength": 2,
          "description": "Words of the company name."
        }
      }
    }
    arguments 21 lines
  • search unknown never probed

    Standard search tool: finds medical devices in the DevicErts catalogue and returns up to 10 results as id, title and url. The id goes to fetch.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 2,
          "description": "Search text."
        }
      }
    }
    arguments 15 lines
  • fetch unknown 21m ago

    Standard fetch tool: the full record behind a search result id (device:<slug> or manufacturer:<slug>) as Markdown text, with its canonical url and metadata (registries, retrieval date, reuse terms).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "maxLength": 260,
          "minLength": 1,
          "description": "A result id from search, such as device:<slug>."
        }
      }
    }
    arguments 15 lines
  • find_device_by_identifier unknown 21m ago

    Exact lookup of a regulatory identifier: 510(k), PMA or De Novo number, UDI-DI or EU Basic UDI-DI. Returns the devices whose primary reference or UDI-DI is that identifier (exact_matches) and devices that carry it elsewhere (related; a Basic UDI-DI or a submission number usually covers several device models).

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "identifier"
      ],
      "properties": {
        "identifier": {
          "type": "string",
          "maxLength": 60,
          "minLength": 4,
          "description": "A 510(k) number (K123456), PMA number (P123456), De Novo number (DEN123456), UDI-DI (GS1 GTIN such as 00884838023703, or HIBCC) or EU Basic UDI-DI. Spaces and letter case are ignored."
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 8d44a396dc9236b7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8d44a396dc9236b7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/8d44a396dc9236b7/badge.svg)](https://brick.blue/agent/8d44a396dc9236b7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.