setup-immune-compass-remote-tool

Deploys and validates the immune COMPASS model as a ToolUniverse remote MCP tool.

1.7k|254|Updated Mar 3, 2025
One-click install
npx skills add https://github.com/mims-harvard/ToolUniverse --skill setup-immune-compass-remote-tool
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-immune-compass-remote-tool
Source: https://github.com/mims-harvard/ToolUniverse/tree/main/skills/setup-immune-compass-remote-tool
Command: npx skills add https://github.com/mims-harvard/ToolUniverse --skill setup-immune-compass-remote-tool

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fastmcp, pyyaml, tuplatform-connect, torch.

What problem does it solve?

Deploying the immune COMPASS immunotherapy-response model as a shared remote tool involves unsafe checkpoint formats, environment drift, and unverified endpoints. This Skill walks you through provisioning safe safetensors weights, launching a loopback MCP server, validating discovery, and optionally relaying it through ToolUniverse Connect.

Core Features & Use Cases

  • Safe checkpoint provisioning: Converts the official COMPASS whole-object checkpoint into a verified safetensors artifact with pinned SHA-256 and upstream revision, so the live server never calls torch.load.
  • Local deployment and validation: Starts the Streamable HTTP MCP endpoint on 127.0.0.1:7003 and verifies tool discovery and a known GIDE sample prediction.
  • Private sharing via ToolUniverse Connect: Uses tu remote login and tu remote share with browser device authorization to publish a private relay without copying keys.
  • Use Case: A computational biology team wants to expose COMPASS responder predictions to collaborators. They follow this Skill to convert the checkpoint, launch the CPU server, run the verified example, and share it privately through the TU Platform.

Quick Start

Ask your AI agent to set up and validate the immune COMPASS remote tool from the ToolUniverse repository root, starting with the preflight contract check.

Frequently Asked Questions about setup-immune-compass-remote-tool

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy the COMPASS model as a remote MCP tool?

Create an isolated Python 3.12 virtual environment, install the immune_compass requirements, convert the official checkpoint to safetensors with the pinned SHA-256, then run python -m tooluniverse.remote.immune_compass.compass_tool to serve the MCP endpoint on 127.0.0.1:7003.

How do I share a private ToolUniverse remote tool?

Run tu remote login once to complete browser device authorization, then run tu remote share immune-compass. The command starts the loopback endpoint, validates discovery, and keeps the relay in the foreground without copying any keys.

Why does the COMPASS server avoid torch.load at runtime?

The live server loads only safetensors, JSON metadata, and an allow_pickle=False preprocessing NPZ to avoid executing arbitrary objects from whole-object checkpoints. Checkpoint conversion happens once in an isolated provisioning environment with digest verification.

Can I run the COMPASS remote tool on GPU?

The validated deployment uses CPU only. Switching devices requires a separate equivalence and resource test comparing class probabilities and all 44 concept scores before changing COMPASS_DEVICE.

What causes 401 or 403 errors on the remote tool endpoint?

A non-loopback bind requires a matching TOOLUNIVERSE_API_TOKEN bearer credential. The recommended setup binds to loopback and shares through the relay instead of exposing the port directly.