A
licenseNot graded
qualityC
maintenanceEnables LLMs to retrieve segment, field, message-structure, and code-table details; parse pipe-delimited messages; and validate messages with deep profiles for ORM^O01, ADT^A08/A31/A40, and ORU^R01.
MIT
DICOM/HL7/FHIR Interoperability MCP Server
by NyxToolsDev
Related Servers
Alternatives to DICOM/HL7/FHIR Interoperability MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceExposes DICOM operations as tools for AI agents to interact with medical imaging systems and PACS. It enables searching for studies and series, querying instance metadata, and retrieving pixel data from DICOM entities.-
- AlicenseNot gradedqualityBmaintenanceEnables standardized PACS-AI integration through the Model Context Protocol, providing medical imaging workflows with DICOMweb transport, hierarchical PHI de-identification, and AI model orchestration.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query, read, download, and move medical imaging data on DICOM servers (PACS, VNA) including patient searches, study retrieval, PDF report extraction, and image transfer to AI endpoints for analysis.MIT
- AlicenseNot gradedqualityBmaintenanceEnables healthcare systems to parse HL7 v2 messages, convert them to FHIR R4 Bundles, validate FHIR resources, and detect/govern PHI with HIPAA, EU MDR, and GDPR compliance evidence for AI governance.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to query and read data on DICOM servers (PACS, VNA, etc.).91MIT
TDQS
A3.8/5.0
Scored across 17 tools
Disambiguation4/5
Tools are generally well-differentated by resource and action, though 'lookup_dicom_tag' and 'explain_dicom_tag' could be confused (前者 is for dictionary lookup by number/keyword, latter for detailed educational context). Similarly, 'pacs_get_metadata' and 'pacs_study_summary' both retrieve study data but serve different use cases (raw metadata vs interoperability mapping). Overall boundaries are clear enough for correct selection.
Naming Consistency4/5
Strong verb_noun convention throughout (e.g., decode_private_tags, explain_hl7_segment, validate_hl7_message). The PACS tools consistently use the 'pacs_' prefix, though 'pacs_study_summary' breaks the otherwise consistent pacs_verb/pacs_verb_noun pattern used by pacs_echo, pacs_query, and pacs_retrieve. Mapping tools follow consistent 'map_x_to_y' structure.
Tool Count4/5
With 17 tools, the set slightly exceeds the ideal 3-15 range, but this is reasonable given the server covers three distinct healthcare standards (DICOM, HL7 v2, FHIR) plus PACS operations. Each tool addresses a specific interoperability need without redundancy; no obvious candidates for merging exist without losing clarity.
Completeness4/5
Covers the full interoperability lifecycle well: DICOM tag inspection, HL7 parsing/validation, bidirectional mapping between standards, PACS connectivity/query/retrieve, and integration pattern guidance. Minor gaps include lack of direct FHIR resource operations (only mapping to FHIR is provided) and no HL7 message transmission capabilities, though these may be outside the server's documentation-focused scope.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive