DICOM/HL7/FHIR Interoperability MCP Server
Bridges DICOM, HL7v2, and FHIR with cross-standard mapping and optional PACS connectivity.
4 stars29 downloads/wk
Reviews
Write oneNobody has reviewed DICOM/HL7/FHIR Interoperability MCP Server yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
DICOM/HL7/FHIR Interoperability MCP Server tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan28 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 60 days ago12/15
- Maintainer identityregistry namespace matches repository owner6/10
How DICOM/HL7/FHIR Interoperability MCP Server compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,273 servers
- GitHub stars
- 4
- more than 82% of 28,534 servers
- Downloads a week
- 29
- more than 18% of 11,915 servers with a package
Install DICOM/HL7/FHIR Interoperability MCP Server in Claude Code, Cursor or VS Code
claude mcp add dicom-hl7-mcp-server -- uvx dicom-hl7-mcp
What the publisher says
From the DICOM/HL7/FHIR Interoperability MCP Server repository's README, as published. We do not edit it. Read it on GitHub
DICOM/HL7/FHIR Interoperability MCP Server
<!-- mcp-name: io.github.NyxToolsDev/dicom-hl7-mcp-server -->
The only MCP server that bridges DICOM, HL7v2, and FHIR in one package — with optional PACS connectivity.
Built by a healthcare IT engineer with 16 years of PACS, RIS, and integration experience. This isn't a wrapper around a FHIR API or a DICOM tag dictionary — it's the interoperability knowledge that takes years on the job to build, plus the ability to connect to real PACS systems.
What Makes This Different
Tools
Reference Tools (Free)
Mapping & Generation Tools (Premium)
PACS Connectivity Tools (Premium)
Installation
Reference tools only (no PACS connectivity):
pip install dicom-hl7-mcpWith PACS connectivity (adds pynetdicom + httpx):
pip install dicom-hl7-mcp[pacs]Configuration
Basic (Reference Tools Only)
Add to your Claude Desktop config:
macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json Windows: %APPDATA%\Claude\claudedesktopconfig.json
{
"mcpServers": {
"dicom-hl7-assistant": {
"command": "uvx",
"args": ["dicom-hl7-mcp"]
}
}
}With Premium License
{
"mcpServers": {
"dicom-hl7-assistant": {
"command": "uvx",
"args": ["dicom-hl7-mcp"],
"env": {
"DICOM_HL7_LICENSE_KEY": "your-license-key-here"
}
}
}
}With PACS Connectivity (Traditional DICOM)
Connect to a PACS using C-FIND/C-MOVE/C-ECHO:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
DICOM/HL7/FHIR Interoperability MCP Server: common questions
- Is DICOM/HL7/FHIR Interoperability MCP Server safe?
- Mostly: it is graded B (75/100). Read the DICOM/HL7/FHIR Interoperability MCP Server safety report
- How do I install DICOM/HL7/FHIR Interoperability MCP Server?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does DICOM/HL7/FHIR Interoperability MCP Server need an API key?
- Yes. The registry entry asks for
DICOM_HL7_LICENSE_KEY. - Is DICOM/HL7/FHIR Interoperability MCP Server maintained?
- The last commit was 96 days ago (2026-07-29). The latest release is v0.2.0.
- How does DICOM/HL7/FHIR Interoperability MCP Server compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,273 servers); github stars 4 (more than 82% of 28,534 servers); downloads a week 29 (more than 18% of 11,915 servers with a package). Full comparison.