EUDAMED MCP
Related Servers
Alternatives to EUDAMED MCP
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityCmaintenanceEnables read-only search and comparison of compliance audit firms and GRC/security AI agents, with lookups cross-checked against official registries.1MIT- AlicenseNot gradedqualityBmaintenanceEnables read-only preflight checks of supplier-declared EPREL records, including product search, record and energy-label lookup, metric comparison, and signed receipts of checked lookups.MIT
- AlicenseNot gradedqualityBmaintenanceEnables free, read-only checks of AI agents and MCP servers for conformance, published changes, delivery evidence, and verifiable receipts without requiring an account or API key, using public or non-personal data only.MIT
- FlicenseNot gradedqualityBmaintenanceEnables read-only access to public U.S. healthcare market-intelligence datasets, including catalogs, schemas, metadata, checksums, and artifact URLs. It supports CMOs, analysts, researchers, and AI agents in discovering and consuming governed market observations without patient-level data.-
- AlicenseNot gradedqualityBmaintenanceEnables local read-only retrieval and search across 27 global medical device regulatory knowledge hubs (NMPA/FDA/MDR/PMDA etc.) using four MCP tools, with zero credentials and no external network calls.1Apache 2.0
- AlicenseCqualityCmaintenanceEnables AI assistants to query ClinicalTrials.gov and PubMed for research evidence, and to compare regulatory document changes against internal files, with strict read-only access and no ability to modify or export data.5Apache 2.0
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.