Skip to main content
Glama

Related Servers

Alternatives to dicom-agent-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query, read, download, and move medical imaging data on DICOM servers (PACS, VNA) including patient searches, study retrieval, PDF report extraction, and image transfer to AI endpoints for analysis.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to query and analyze medical imaging metadata from DICOM servers, including patient information, studies, series, and instances, as well as extract text from encapsulated PDF documents.
      105
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables standardized PACS-AI integration through the Model Context Protocol, providing medical imaging workflows with DICOMweb transport, hierarchical PHI de-identification, and AI model orchestration.
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that exposes a DICOMweb-compliant DICOM archive to AI assistants. It lets any MCP-capable client search studies, series and instances, inspect metadata, read Structured and Encapsulated PDF Reports, and render image frames — all through natural language.
      9
      106 npm
      4
      MIT

    TDQS

    A3.5/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct DICOM operations or local resources. The only potential overlap is among retrieve, move, store, and transfer, but their descriptions distinguish DIMSE/DICOMweb and cache-based workflows well enough.

    Naming Consistency4/5

    The set is mostly snake_case and follows a predictable verb_noun pattern for local and analytical operations. The single-verb network tools (echo, search, retrieve, move, store, transfer) are standard DICOM terms, so the deviation is minor and readable.

    Tool Count4/5

    At 16 tools it is slightly above the typical 3-15 range, but the DICOM domain justifies the breadth: network operations, local cache inspection, rendering, measurement, geometry checks, and de-identification are all represented. Each tool appears to earn its place.

    Completeness4/5

    The surface covers the core DICOM lifecycle: node discovery, connectivity, query/retrieve, move/store/transfer, local metadata, rendering, measurement, geometry validation, and de-identification. Minor gaps like local cache cleanup or more granular de-identification configuration are not blocking for likely agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues