DICOM MCP
Queries, reads, and moves data on DICOM servers such as PACS and VNA, extracting reports and searching patient metadata.
Delv Safety Grade: C
Score 58/100 · assessed 2026-04-28
DICOM MCP is a community server enabling Claude to interact with medical imaging infrastructure (PACS/VNA systems). It's maintained by a solo developer (Christian Hinge) with limited visible activity, creating bus factor concerns for healthcare-critical tooling. The server handles highly sensitive patient data and medical imaging, yet requires network access to hospital systems without clear documentation on authentication, encryption, or HIPAA compliance measures. Supply chain is reasonable via PyPI, but the narrow maintainer base and healthcare context elevate risk. The permissions footprint is substantial: network access to private medical networks, potential PHI exposure, and data movement capabilities. Transparency is adequate with open source code, but lacks security audit trails or compliance documentation. No known incidents, but the combination of solo maintenance and healthcare data handling warrants careful vetting before production use.
Lethal Trifecta (prompt-injection exposure)
ONE OF THREEMedical imaging is sensitive private data. No untrusted input or outbound by default.
Green flags
- Open source with visible codebase on GitHub
- Distributed via standard PyPI package manager
- Addresses genuine clinical informatics need (DICOM protocol bridge)
- No known security incidents or CVEs
Red flags
- Solo maintainer for healthcare-critical infrastructure handling PHI
- Network access to private medical systems (PACS/VNA) without clear auth docs
- No visible HIPAA compliance documentation or security audit
- Data movement capabilities across medical imaging nodes risk PHI leakage
- Limited maintenance activity for mission-critical healthcare tooling
Permissions requested
Install
uv tool install dicom-mcp
Review
Install this if you're building clinical AI tools or need programmatic access to PACS data from Claude. Skip it if you're not in healthcare or don't have a DICOM server to connect to. It's a specialist tool for a specialist audience, but it's the only MCP server doing this job.
Good at
- Only MCP server that speaks native DICOM protocol, filling a real gap for clinical AI workflows.
- Handles C-FIND, C-MOVE, and C-GET operations, covering the core PACS query and retrieval tasks.
- Useful for auditing, report extraction, and building custom interfaces over legacy imaging systems.
- No environment variables required, keeping the config surface small.
Watch out
- Requires access to a DICOM server, making it impossible to demo or test without healthcare infrastructure.
- Minimal documentation assumes you already understand DICOM networking and AE title configuration.
- DICOM protocol itself is notoriously fiddly, so expect setup friction with ports and firewall rules.
- No built-in image analysis or pixel-level processing, purely metadata and report retrieval.
Use cases
- radiology workflows
- PACS querying
- medical image retrieval
- clinical report extraction
Getting started
Works with
Similar MCPs
- DaVinci Resolve MCPFull coverage of the DaVinci Resolve scripting API so agents can drive timelines, edits, colour grading, and media management via Claude.
- Free Will MCPExperimental tools that let an AI give itself prompts, ignore user requests, or go to sleep, for studying autonomy.
- Godot MCPInteracts with the Godot game engine for scene editing, running, debugging, and project management.
- QGIS MCPConnects QGIS Desktop to Claude for prompt-assisted project creation, layer loading, and code execution.