MCP servers › com.devicerts › medical-devices
MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19
medical-devices MCP server
Registry name com.devicerts/medical-devices
deviCERTS medical device regulatory data — the publisher's title
by devicerts.com · domain (the registry's namespace rule)repository owner on GitHub: dutracki (personal account)Source ↗Website ↗
FDA 510(k)/PMA/De Novo, GUDID, recall and EUDAMED device and certificate data. Read-only, no login. — the publisher's description
Summary
com.devicerts/medical-devices is a remote MCP server listed in the official MCP registry at version 1.2.0, under the namespace of the domain devicerts.com. Its linked repository is github.com/dutracki/devicerts-mcp; GitHub reports its owner as dutracki, a personal account. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 15 tools, 0 resources and 0 prompts.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 15
- Last tested
- 2026-11-19
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-19 (devicerts.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (1.2.0).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-19
- Mode
- read-only (no tool calls)
- Latest version
- 1.2.0, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
- First listed version
- 2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-11-16 to 2026-11-18; 3 in the 90 days before the 2026-11-19 snapshot.(versions still listed in the registry only)
Most recent 3 versions
1.2.0· 2026-11-181.1.0· 2026-11-161.0.0· 2026-11-16
- Registry data
- snapshot 2026-11-19
- Package and repository
- checked 2026-11-19
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 1.1.0 (published 2026-11-16) → 1.2.0 (published 2026-11-18), between the registry lists of 2026-11-18 and 2026-11-19.
The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.
Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.
What it is
What does this server offer?
Observed inventoryNone of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.
- search_deviceson 8 other servers
“Search the DevicErts medical device catalogue by text, with filters for registry, region, risk class and manufacturer, and offset paging.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 1 required
querystringrequired“Search text, 2 to 200 characters: device or trade name, device type, model or catalogue number, or manufacturer name.”registrystring“Only devices listed in this registry: eudamed (EU), fda_510k (FDA 510(k) and De Novo), fda_pma (FDA PMA) or fda_udi (FDA GUDID).”regionstring“Only devices listed in a registry of this region: EU (EUDAMED) or US (any FDA registry: 510(k), De Novo, PMA, GUDID).”manufacturerstring“Only devices of manufacturers whose name contains these words, 2 to 100 characters.”device_classstring“Only devices of this risk class, as stored: EU MDR/MDD Class I, IIa, IIb, III; US FDA Class I, II, III; EU IVDR Class A to D; AIMDD (EU active implantables); t…”limitinteger“Results per page, integer 1 to 20.”offsetinteger“Number of results to skip, integer 0 to 999.”
- find_device_by_identifier
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
identifierstringrequired“One regulatory identifier, 4 to 60 characters: a 510(k) number (e.g.”
- get_deviceon 14 other servers
“Get the DevicErts record of one device by slug.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
slugstringrequired“Device slug: the last part of its https://devicerts.com/devices/<slug> URL, as returned by search_devices or find_device_by_identifier.”detailstring“summary (default): names, manufacturer, status, class, authorizations.”
- get_device_recalls
“List the U.S.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
slugstringrequired“Device slug: the last part of its https://devicerts.com/devices/<slug> URL, as returned by search_devices or find_device_by_identifier.”statusstring“Only recalls with this FDA status: ongoing, completed or terminated.”
- get_device_certificates
“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 a…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
slugstringrequired“Device slug: the last part of its https://devicerts.com/devices/<slug> URL, as returned by search_devices or find_device_by_identifier.”
- search_recallson 14 other servers
“Search U.S.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
11 inputs
querystring“Words in the product description, recall reason, recalling firm or recall number, 2 to 200 characters.”product_codestring“Only recalls of this three-letter FDA product code.”firmstring“Only recalls whose recalling firm name contains these words, 2 to 100 characters.”submission_numberstring“Only recalls naming this FDA submission: a 510(k), PMA, De Novo or HDE number.”pathwaystring“Only recalls naming a submission of this FDA premarket pathway: 510k, pma or denovo.”date_fromstring“Only recalls started on or after this date, YYYY-MM-DD.”date_tostring“Only recalls started on or before this date, YYYY-MM-DD.”recall_classstring“Only recalls of this FDA recall class: Class I (most serious), Class II or Class III.”statusstring“Only recalls with this FDA status: ongoing (open), completed or terminated.”limitinteger“Results per page, integer 1 to 20.”offsetinteger“Number of results to skip, integer 0 to 999.”
- search_certificateson 2 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
9 inputs
numberstring“Certificate number or its beginning, 2 to 60 characters; spaces are ignored.”notified_bodystring“Notified body: its four-digit number (e.g.”manufacturerstring“Certificate holder: words of its name (e.g.”legislationstring“Only certificates under this EU regulation: MDR (medical devices) or IVDR (in vitro diagnostics).”statusstring“Only certificates with this current EUDAMED status: issued, supplemented, amended, reissued, reinstated, restricted, suspended, cancelled or withdrawn.”valid_onstring“Only certificates whose validity period (start to expiry) covers this date, YYYY-MM-DD.”include_removedboolean“true: also certificates EUDAMED no longer lists.”limitinteger“Results per page, integer 1 to 20.”offsetinteger“Number of results to skip, integer 0 to 999.”
- search_manufacturerson 2 other servers
“Search medical device manufacturers by company name, optionally in one country, with offset paging.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
querystringrequired“Words of the company name, 2 to 100 characters.”countrystring“Only manufacturers registered with this country in a registry (EUDAMED or FDA address): a two-letter ISO 3166-1 alpha-2 code.”limitinteger“Results per page, integer 1 to 20.”offsetinteger“Number of results to skip, integer 0 to 999.”
- get_manufactureron 1 other server
“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, …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
slugstringrequired“Manufacturer slug: the last part of its https://devicerts.com/manufacturers/<slug> URL, as returned by search_manufacturers or get_device.”
- get_data_sourceson 6 other servers
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- search_gudid_listings
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs, 1 required
querystringrequired“Search text, 2 to 200 characters: a UDI-DI (GS1 GTIN or HIBCC), a brand or trade name, a version or model, or the labeler (company) name.”companystring“Only listings of labelers whose name contains these words, 2 to 100 characters.”limitinteger“Results per page, integer 1 to 20.”offsetinteger“Number of results to skip, integer 0 to 999.”
- get_recallon 1 other server
“Get one U.S.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
recall_numberstringrequired“The FDA recall number, 3 to 40 characters; letter case and spaces are ignored.”
Show 3 more tools
- search_establishmentson 1 other server
“Search registered establishments: EU economic operators and authorities in EUDAMED (manufacturers, authorised representatives, importers, notified bodies, competent authorities, sponsors) by name, SR…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 1 required
querystringrequired“Establishment name (2 to 100 characters), an EUDAMED SRN (e.g.”registrystring“eudamed: EU economic operators and authorities with an SRN, searched by name or SRN.”actor_typestring“Only EUDAMED operators of this role: Manufacturer, Authorised Representative, Importer, Notified Body, Competent Authority or Sponsor.”countrystring“Only EUDAMED operators registered in this country: a two- or three-letter country code.”limitinteger“Results per page, integer 1 to 20.”offsetinteger“Number of results to skip, integer 0 to 999.”
- searchon 1,102 other servers
“Search devices in the standard search/fetch connector format: up to 10 results as id, title and url; each id goes to fetch.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
querystringrequired“Search text, 2 to 200 characters: device name, type, model or manufacturer.”
- fetchon 649 other servers
“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 (retri…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
idstringrequired“A result id from search: device:<slug> or manufacturer:<slug>.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-19.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 51
- Tools with a description
- 100% of 15
- Typical description length
- 757 characters
The tool set
Counted from the listing
- Tools
- 15
- Size of the list
- about 9,364 tokens for an agent to load (characters ÷ 4)
- Naming
- 13 of 15 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 15 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-19 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://devicerts.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"medical-devices": {
"url": "https://devicerts.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"medical-devices": {
"type": "http",
"url": "https://devicerts.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"medical-devices","type":"http","url":"https://devicerts.com/mcp"}'Claude Code
claude mcp add --transport http medical-devices https://devicerts.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"medical-devices": {
"type": "streamableHttp",
"url": "https://devicerts.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"medical-devices": {
"httpUrl": "https://devicerts.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.medical-devices] url = "https://devicerts.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"medical-devices": {
"url": "https://devicerts.com/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://devicerts.com/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
- Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.
Own host
- security.txt. No security.txt at https://devicerts.com/.well-known/ (HTTP 404, 2026-11-19). Source: devicerts.com/.well-known/security.txt · read 2026-11-19.
- A2A agent card. No A2A agent card at https://devicerts.com/.well-known/ (HTTP 404, 2026-11-19). Source: devicerts.com/.well-known/agent-card.json · read 2026-11-19.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint devicerts.com/mcp | Session opened | matches | our test · 2026-11-19 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-19 |
| Repository github.com/dutracki/devicerts-mcp | Opens publicly | matches | api.github.com · 2026-11-19 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- com.devicerts
- GitHub owner
- a personal account (dutracki)
- Repository
- github.com/dutracki/devicerts-mcp
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-16.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Tool list changes
Our reads compared · no tool calledHosted endpoint devicerts.com/mcp
2 of 2 comparisons between consecutive reads showed a change (3 reads, 2026-11-16 to 2026-11-19; versions 1.0.0 to 1.2.0).
Last change seen between our reads on 2026-11-17 (version 1.1.0) and 2026-11-19 (version 1.2.0).
Added (3):
get_recallsearch_establishmentssearch_gudid_listingsCompared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-19 is not known yet. No tool was called. How it is compared
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-16). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about com.devicerts/medical-devices
Answered from the data aboveWho publishes com.devicerts/medical-devices?
The registry ties the namespace com.devicerts to the domain devicerts.com; only its owner can publish under it. Its linked repository is github.com/dutracki/devicerts-mcp; GitHub reports its owner as dutracki, a personal account. These are facts from the registry and GitHub, not a rating.
Is com.devicerts/medical-devices safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does com.devicerts/medical-devices need an API key or sign-in?
It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.devicerts/medical-devices been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.
Does com.devicerts/medical-devices publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of com.devicerts/medical-devices?
In github.com/dutracki/devicerts-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (no operator permission)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so). This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,247 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 15 tools, 0 resources, 0 prompts.
- 3,703 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.devicerts/medical-devices: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/com.devicerts/medical-devices
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.devicerts/medical-devices)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology