Server

DICOMweb MCP Server

Published by PantelisGeorgiadis. Transport: stdio (local). Written in typescript.

Cross-source (2 sources)

View source on GitHub Scan status Methodology

Description

Description below is sourced from the LF AAIF MCP registry. MCPowered surfaces the publisher's own words; the publisher is the warrantor of any claims they make.

MCP server exposing a DICOMweb DICOM archive to AI assistants via QIDO-RS and WADO-RS.

Provenance

Server id: github/pantelisgeorgiadis/dicomweb-mcp-server
Repository: pantelisgeorgiadis/dicomweb-mcp-server
Package: npm:dicomweb-mcp-server
Surfaced by: awesome-mcp-servers , LF AAIF registry
Category: Biology, Medicine and Bioinformatics

Scan status

Code axis

99 / 100

Higher is fewer findings; see how the code axis is computed.

Last scanned 2026-05-28T14:12:32Z

Source hash f9faa92a865b

Total findings 1 · 0 critical · 0 warning · 1 informational

Checks run Tool description scan , Tool output literal scan , Dependency CVE check , Permission audit

Findings

informational permission_audit methodology

src/utils/query.js:105

Matched fetch(

Suggested action The server makes outbound network calls. Verify the documented destination list matches.

Patterns network-out

What we couldn't check

dynamic_tool_descriptions
Static analysis only sees descriptions hardcoded in source. Servers that compute descriptions at runtime (server-generated tools/list responses) are not covered by Check 1 at v0.
ast_indirection
v0 regex sees only literal description strings. Descriptions assembled by concatenation or pulled through variable indirection evade detection until AST-level extraction lands in v1.

Install configuration

Universal install-config generation across agent clients (Claude Code, Cursor, Windsurf, ChatGPT Apps, Continue, Cline, Zed) is a v0 deliverable. For now, install per the publisher's repository instructions linked above. The auto-generated client-specific configuration block lands here when the install-config generator ships.

Disclaimer

Scan results describe what our static checks found and didn't find at the time of scan. They are not a recommendation, certification, or guarantee. A scanned-clean result is the absence of evidence of malice, not the presence of evidence of integrity. Servers can be compromised after scan. You are responsible for evaluating whether to install any MCP server. See our methodology for what we check, what we can't check, and the limits of static analysis.

MCPowered