EUDAMED MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EUDAMED_BASE_URL | No | HTTPS endpoint, without credentials, query or fragment. | https://api.datalake.sante.service.ec.europa.eu/eudamed |
| EUDAMED_MAX_PAGES | No | 1–50 pages per query; combined record cap 10,000. | 10 |
| EUDAMED_TIMEOUT_MS | No | 1–120000; each request attempt including body reads. | 15000 |
| EUDAMED_API_VERSION | No | Version string such as `v1.0`. | v1.0 |
| EUDAMED_MAX_RETRIES | No | 0–3 retries after the initial attempt. | 2 |
| EUDAMED_CACHE_TTL_MS | No | 0–86400000; device/actor response TTL. | 60000 |
| EUDAMED_REFERENCE_TTL_MS | No | 0–86400000; reference response TTL. | 3600000 |
| EUDAMED_MAX_RESPONSE_BYTES | No | 1–50000000; streamed body cap. | 10000000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| eudamed_devicesA | Search public UDI records by at least one restrictive filter. Upstream name matching is not guaranteed to be partial; exact=true additionally matches every supplied filter locally. Returns normalized evidence and source provenance; raw=true adds original device fields. No exhaustive-coverage or conformity guarantee. |
| eudamed_actorsA | Look up an exact actor SRN or four-digit notified body ID. Returns organizational identity, role, country and status; excludes personal names, addresses and contact details. |
| eudamed_discover_actorsA | Resolve a company name using exact legal and abbreviated name searches. Returns deduplicated organizational candidates, source observations and a public-portal link for partial-name discovery. Confirm legal entity, country and role before using its SRN; never invent or silently pick an ambiguous SRN. |
| eudamed_referencesA | Fetch reference values by language, optionally filtering CODE and ID together. Local limit only; use CODE + ID as the join key, never ID alone. |
| eudamed_investigateA | Bounded device investigation: verify supplied manufacturer, search identifiers first and names separately, discover actual manufacturers, inspect portfolios and representatives, decode fields and list unverified documents. Separates target evidence from portfolio context, reports identity conflicts, and returns a concise report plus detailed JSON. Preserves failures, provenance and bounds. No certificate/IFU retrieval or conformity decision. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| investigate_device | Investigate device identity, operators and evidence gaps using public EUDAMED records. |
| manufacturer_portfolio | Inspect a bounded manufacturer portfolio and verify the economic operator. |
| conformity_evidence | Prepare a device evidence checklist without making a conformity determination. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| search-guide | EUDAMED search guide |
| evidence-guide | EUDAMED evidence guide |
| investigate_device | Investigate device identity, operators and evidence gaps using public EUDAMED records. |
| manufacturer_portfolio | Inspect a bounded manufacturer portfolio and verify the economic operator. |
| conformity_evidence | Prepare a device evidence checklist without making a conformity determination. |
TDQS
Scored across 5 tools
The five tools mostly target distinct operations: device search, exact actor lookup, actor name discovery, reference lookup, and bounded investigation. The main overlap is between eudamed_devices and eudamed_investigate, since investigation also searches devices, but the composite/multi-step scope is described clearly enough to distinguish them. Actor lookup versus actor discovery is well separated by exact-ID versus name-resolution intent.
All names use the eudamed_ prefix and snake_case, which is predictable. However, the set mixes noun-style resource names (eudamed_devices, eudamed_actors, eudamed_references) with action-style names (eudamed_discover_actors, eudamed_investigate), so the verb_noun convention is not fully consistent.
Five tools is well within the appropriate range for a focused public-data lookup server. Each tool covers a distinct slice of the domain, and the composite investigation tool avoids needing many narrow follow-up tools.
The surface covers device UDI search, actor lookup and discovery, reference values, and bounded investigation, which is solid for public EUDAMED exploration. The main explicit gaps are certificate/IFU/document retrieval, but the investigate tool acknowledges these limits so agents can recognize the boundary.