MCP Catalogs
HomeSTAMP screenshot

STAMP

by KatherLab·119·Score 47

STAMP is a computational pathology tool with MCP support for histopathology image analysis and biomarker prediction.

ai-llmdeveloper-toolsother
53
Forks
13
Open issues
this month
Last commit
2d ago
Indexed

Overview

STAMP is an end-to-end, weakly-supervised deep learning pipeline designed for histopathology image analysis. It provides a complete workflow from whole-slide image processing to biomarker prediction without requiring pixel-level annotations. The tool supports multiple foundation models and can handle classification, regression, and survival analysis tasks. With MCP support, STAMP can be integrated into AI workflows as an intelligent tool for computational pathology research.

Try asking AI

After installing, here are 7 things you can ask your AI assistant:

you:Automating biomarker discovery from histopathology slides
you:Predicting patient survival based on pathology images
you:Assessing disease activity from tissue sections
you:Cancer subtyping from H&E stains
you:Risk stratification in breast cancer patients
you:What computational resources are required for STAMP?
you:How does STAMP's MCP integration work?

When to choose this

Pathology researchers needing a validated, peer-reviewed workflow for biomarker discovery from whole-slide images.

When NOT to choose this

If you need immediate MCP integration; STAMP only mentions MCP support as a future feature without implementation.

Tools this server exposes

9 tools extracted from the README
  • init

    Create a new STAMP configuration file

  • preprocess

    Preprocess whole-slide images into feature vectors

  • encode_slides

    Encode patch-level features into slide-level embeddings

  • encode_patients

    Encode features into patient-level embeddings

  • train

    Train a Vision Transformer model

  • crossval

    Train a Vision Transformer model with cross validation

  • deploy

    Deploy a trained Vision Transformer model

  • statistics

    Generate AUROCs and AUPRCs with 95%CI for a trained model

  • heatmaps

    Generate heatmaps for a trained model

Note: Tool names extracted from CLI documentation but no MCP-specific tool signatures provided. MCP support is mentioned but not detailed in this README.

Comparable tools

histopathology-aidigital-pathology-workflowbioimage-analysis-pipeline

Installation

Installation

STAMP requires [uv](https://docs.astral.sh/uv/) for installation. The project supports both CPU and GPU installations with multiple options:

# Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh

# Clone and setup STAMP
git clone https://github.com/KatherLab/STAMP.git
cd STAMP

# GPU installation
uv sync --extra gpu
source .venv/bin/activate

# CPU installation
uv sync --extra cpu
source .venv/bin/activate

For Claude Desktop integration:

{
  "mcpServers": {
    "stamp": {
      "command": "uv",
      "args": ["run", "--package", "stamp", "--", "mcp"],
      "env": {
        "PYTHONPATH": "/path/to/STAMP"
      }
    }
  }
}

FAQ

What computational resources are required for STAMP?
STAMP can run on both CPU and GPU systems. GPU installation requires CUDA 13.0 and a compatible NVIDIA driver (version 580 or newer). The tool is designed to handle large datasets and can be deployed on HPC systems with SLURM.
How does STAMP's MCP integration work?
STAMP includes an 'mcp/' module that enables integration with Model Context Protocol. This allows the tool to function as an MCP server, exposing its computational pathology capabilities to AI workflows.

Compare STAMP with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.