← Explore all mcp servers

AWS DATA SERVICES / AWS Labs

AWS Labs HealthImaging

Searches and manages medical imaging datastores, image sets and DICOM lifecycle operations.

“The AWS HealthImaging MCP Server enables AI assistants to interact with AWS HealthImaging services through the Model Context Protocol (MCP).”

01 / THE REASONING

Why this made the selection.

  • Specialized publisher integration with documented IAM and data access boundaries.
  • Inspect image-set metadata and import-job status in an authorized test datastore.
  • The catalogue does not already have src/healthimaging-mcp-server/README.md.
  • The README documents irreversible image-set deletion and patient-study deletion, and the install examples do not pass a read-only flag.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • src/healthimaging-mcp-server/README.md
  • src/healthimaging-mcp-server/pyproject.toml
  • src/healthimaging-mcp-server/awslabs/healthimaging_mcp_server/server.py
  • Root README.md and LICENSE
  • LICENSE

Our findings

  • Pinned server.py has unconditional tool registrations for create_datastore, delete_datastore, bulk_delete_by_criteria and retrieval operations. No read-only argument was identified in its startup.
  • The overview says 39 specialized tools, and a later sentence says 39 tools in eight categories. It also says 21 standard API operations and 18 advanced DICOM operations, which sum to 39.
  • Counted in this file, the eight category headings sum to 36. The bullet lines under them sum to 38: Datastore Management says 4 tools and lists 3, and Data Analysis Operations says 8 tools and lists 11. The other six headings match their bullet counts.
  • delete_image_set is marked IRREVERSIBLE. delete_patient_studies, delete_study, and bulk_delete_by_criteria are also listed. The word readonly does not appear, and read-only does not appear.

Not established by this review

  • Server startup, authentication, live tool execution and security isolation were not tested.
  • Published package/container parity with a source revision and hosted implementation internals were not tested.
  • The resource was not executed and its tools were not called.
  • No HealthImaging API call was made.
  • The tool bullets were counted in the README and were not listed from a running server.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

uvx awslabs.healthimaging-mcp-server@latest

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Configure a read-only AWS role and the intended HealthImaging region before first connection.
  2. List and inspect the exact datastore/image-set identifiers; keep broad delete and bulk update operations outside routine diagnostics.
  3. For an approved transfer or mutation review S3 destinations, role permissions, version selection and returned job status.

Before you start

  • Python 3.10 or newer, uv/uvx and an MCP client that can launch a local stdio process.
  • An AWS account, configured credentials and access to the intended region and service resources.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "awslabs-healthimaging": {
      "command": "uvx",
      "args": [
        "awslabs.healthimaging-mcp-server@latest"
      ],
      "env": {
        "AWS_PROFILE": "YOUR_RESTRICTED_PROFILE",
        "AWS_REGION": "us-east-1"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/healthimaging-mcp-server/README.md

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  2. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/healthimaging-mcp-server/pyproject.toml

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  3. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/healthimaging-mcp-server/awslabs/healthimaging_mcp_server/server.py

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  4. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/README.md

    Supports: summary, install, configExample, access, limitations, bestFor, review, compatibility, transports

  5. Applicable licence ↗Checked

    https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE

    Supports: license

  6. https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/src/healthimaging-mcp-server/README.md

    Supports: tool-count mismatch and delete tools

  7. Repository LICENSE ↗Checked

    https://github.com/awslabs/mcp/blob/8840003820a78dd018561d55c7ab12fcdd708464/LICENSE

    Supports: Apache License Version 2.0

Evidence & Ask