T
t4dhg/mcp-eudamed
Independent, unofficial integration.
updated 2026-11-15
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · t4dhg/mcp-eudamed · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
t4dhg/mcp-eudamed;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
Independent, unofficial integration.
Excerpted from the repository README (abridged)
# EUDAMED MCP
Search European medical-device records from your AI assistant.
Independent, unofficial integration · Read-only access · No API key required for the public endpoints tested
A read-only Model Context Protocol server for the European Commission's EUDAMED Public API. Search UDI records, verify economic operators, decode classification and status values, and investigate a device without losing the distinction between a public record and verified conformity evidence.
Start with a company name, device name or UDI. Find candidate records, identify the registered manufacturer and build an evidence checklist with source links and explicit gaps.
6 tools · 3 guided workflows · 5 readable resources
Get started · Example requests · How evidence works · Official EUDAMED portal
## What makes it useful
Identity before interpretation. Preserve leading zeroes in UDIs, apply exact matching locally, and keep multiple candidates visible.
Find the actual manufacturer. A supplied SRN can belong to another company in the same group. Investigation searches device identity independently and follows the manufacturer SRN in the returned record.
Evidence you can trace. Results carry the exact source query, original retrieval timestamp, API version, cache status and local limits.
Honest gaps. Missing flags remain unknown. Failed requests remain failures. IFUs, declarations and certificates remain unverified until obtained separately.
Small tool surface. Six tools expose the three verified API endpoints and a bounded investigation workflow. Prompts are also resources, so clients can read the procedures without invoking a slash command.
Conservative by default. Serialized requests, bounded retries, timeouts, response-size limits, short-lived caching and organizational-only actor data.
This is an independent integration, not an official European Commission product. Public registration does not independently establish product conformity. The server does not retrieve IFUs or certificates and does not issue a compliant/non-compliant verdict.
## Install and connect
Requires Node.js 22 or later. Add this entry to your MCP client's server configuration:
json
"mcpServers": {
"eudamed": {
"command": "npx",
"args": ["-y", "@t4dhg/mcp-eudamed"]
To build from source, run npm ci && npm run build in the checkout and configure node with the absolute path to dist/cli.js.
The server uses stdio. Standard output is reserved for MCP messages. No credentials or .env file are needed. Optional configuration is read from the process environment; .env files are not loaded automatically.
For reproducible installs, append @ to the package name using a release from npm.
For programmatic use, import EudamedClient, investigate or createServer from the package. Importing the library does not start a transport:
typescript
import { EudamedClient, investigate } from '@t4dhg/mcp-eudamed';
const api = new EudamedClient();
const results = await api.devices({
primaryDi: 'YOUR_PRIMARY_UDI_DI',
exact: true,
});
const dossier = await investigate(api, {
manufacturerSrn: 'US-MF-000000001',
tradeName: 'YOUR_DEVICE_NAME',
});
## Try these requests
> Find the public EUDAMED record for this Primary UDI-DI. Show the legal manufacturer, authorised representative, risk class and the exact source query.
Search European medical-device records from your AI assistant.
Independent, unofficial integration · Read-only access · No API key required for the public endpoints tested
A read-only Model Context Protocol server for the European Commission's EUDAMED Public API. Search UDI records, verify economic operators, decode classification and status values, and investigate a device without losing the distinction between a public record and verified conformity evidence.
Start with a company name, device name or UDI. Find candidate records, identify the registered manufacturer and build an evidence checklist with source links and explicit gaps.
6 tools · 3 guided workflows · 5 readable resources
Get started · Example requests · How evidence works · Official EUDAMED portal
## What makes it useful
Identity before interpretation. Preserve leading zeroes in UDIs, apply exact matching locally, and keep multiple candidates visible.
Find the actual manufacturer. A supplied SRN can belong to another company in the same group. Investigation searches device identity independently and follows the manufacturer SRN in the returned record.
Evidence you can trace. Results carry the exact source query, original retrieval timestamp, API version, cache status and local limits.
Honest gaps. Missing flags remain unknown. Failed requests remain failures. IFUs, declarations and certificates remain unverified until obtained separately.
Small tool surface. Six tools expose the three verified API endpoints and a bounded investigation workflow. Prompts are also resources, so clients can read the procedures without invoking a slash command.
Conservative by default. Serialized requests, bounded retries, timeouts, response-size limits, short-lived caching and organizational-only actor data.
This is an independent integration, not an official European Commission product. Public registration does not independently establish product conformity. The server does not retrieve IFUs or certificates and does not issue a compliant/non-compliant verdict.
## Install and connect
Requires Node.js 22 or later. Add this entry to your MCP client's server configuration:
json
"mcpServers": {
"eudamed": {
"command": "npx",
"args": ["-y", "@t4dhg/mcp-eudamed"]
To build from source, run npm ci && npm run build in the checkout and configure node with the absolute path to dist/cli.js.
The server uses stdio. Standard output is reserved for MCP messages. No credentials or .env file are needed. Optional configuration is read from the process environment; .env files are not loaded automatically.
For reproducible installs, append @ to the package name using a release from npm.
For programmatic use, import EudamedClient, investigate or createServer from the package. Importing the library does not start a transport:
typescript
import { EudamedClient, investigate } from '@t4dhg/mcp-eudamed';
const api = new EudamedClient();
const results = await api.devices({
primaryDi: 'YOUR_PRIMARY_UDI_DI',
exact: true,
});
const dossier = await investigate(api, {
manufacturerSrn: 'US-MF-000000001',
tradeName: 'YOUR_DEVICE_NAME',
});
## Try these requests
> Find the public EUDAMED record for this Primary UDI-DI. Show the legal manufacturer, authorised representative, risk class and the exact source query.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/t4dhg-mcp-eudamed/)
- Source
- awesome · https://github.com/t4dhg/mcp-eudamed
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.