Model Context Protocol moderate risk

Dicom

The dicom-mcp server allows AI assistants to interact with DICOM servers for querying, reading reports, and moving medical imaging data.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

readwriteexec

Quickstart

Install

npx @modelcontextprotocol/inspector uv run dicom-mcp /path/to/your_config.yaml --transport stdio

Config

{
  "mcpServers": {
    "dicom": {
      "command": "uvx",
      "args": ["dicom-mcp", "/path/to/your_config.yaml"]
    }
  }
}

Exposed MCP Tools (11)

safe

query_patients

Search for patients based on specified criteria.

Read-only operation, no data modification.

safe

query_studies

Find studies based on patient ID, date, or other criteria.

Read-only operation, no data modification.

safe

query_series

Locate series within a study based on modality or description.

Read-only operation, no data modification.

safe

query_instances

Find individual instances within a series.

Read-only operation, no data modification.

safe

extract_pdf_text_from_dicom

Retrieve and extract text from a PDF encapsulated in a DICOM instance.

Read-only operation, no data modification.

moderate

move_series

Send a specific DICOM series to another configured DICOM node.

Involves data transfer, potential for exposure if destination is compromised.

moderate

move_study

Send an entire DICOM study to another configured DICOM node.

Involves data transfer, potential for exposure if destination is compromised.

safe

list_dicom_nodes

Show the active DICOM node and list all configured nodes.

Read-only operation, no data modification.

safe

switch_dicom_node

Change the active DICOM node for subsequent operations.

Configuration change, but does not directly affect data.

safe

verify_connection

Test the DICOM network connection to the active node.

Read-only operation, no data modification.

safe

get_attribute_presets

List the available levels of detail for metadata query results.

Read-only operation, no data modification.

Safety Assessment

The dicom-mcp server is relatively safe for querying and reading DICOM data within a controlled environment. However, the ability to move data to other DICOM nodes introduces a moderate risk, especially if those nodes are not properly secured. It is crucial to configure the server with appropriate network security measures and avoid connecting it to live, unprotected hospital databases.

Configuration file allows specifying allowed DICOM nodes.
No direct internet exposure unless DICOM nodes are externally accessible.
Focus on querying and moving data, rather than direct modification.
Can be used with locally hosted LLMs for data privacy.

Moving DICOM data could potentially expose sensitive information if not handled carefully.
Configuration file requires careful management to prevent unauthorized access.
No built-in authentication mechanism beyond network-level security.
Potential for data leakage if connected to live hospital databases without proper safeguards.
The move_series and move_study tools can send data to external nodes.