What it does
The server provides four tools for healthcare data. parse_hl7v2 reads a pipe-delimited HL7 v2 message and returns its message type and key patient fields. hl7_to_fhir maps an HL7 v2 message to a minimal FHIR R4 message Bundle containing a Patient and a MessageHeader. validate_fhir checks that a FHIR resource is well-formed JSON with a resourceType and a basic structure. govern_phi detects PHI in a message or FHIR resource, reports HIPAA, MDR and GDPR Article 9 risks, and gives data-minimisation advice; its results can be attested on the CSOAI ledger.
It suits teams that need to move legacy HL7 v2 messaging into FHIR and review the PHI it contains before further use. The publisher says it is part of the CSOAI Layer-0 legacy-bridge family, alongside cobol-bridge-mcp, and that it pairs with hipaa-compliance-mcp, healthcare-ai-governance-mcp and eu-ai-act-compliance-mcp, the last for Annex I medical devices.
The documentation does not describe installation steps, runtime requirements or configuration.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CSOAI-ORG/hl7-fhir-bridge-mcp
HL7 v2 / FHIR healthcare bridge — parse, map, validate, govern PHI (HIPAA/MDR).
v0.1.2As shown on registry.modelcontextprotocol.io when we last read it