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.