# Computesage Stackbench MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.computesage%2Fstackbench
Registry id: `mcp-registry/com.computesage/stackbench`
Status: live (checked 2026-10-26T18:39:29.389Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 4934
- Outages (90 days): 0

## Install

```json
{
  "mcpServers": {
    "computesage-stackbench-mcp-server": {
      "type": "http",
      "url": "https://mcp.computesage.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http computesage-stackbench-mcp-server https://mcp.computesage.com/mcp
```

## Tools (5)

- `check_deployment_fit`: $0.01 USDC on Base mainnet: check model/configuration fit against bounded StackBench capacity evidence.
- `generate_launch_config`: $0.50 USDC: generate deterministic vLLM or llama.cpp launch templates from an exact StackBench recommendation without claiming a launch occurred.
- `predict_performance`: $0.05 USDC: predict configuration throughput, memory, and power from bounded StackBench evidence with confidence, missing metrics, and caveats.
- `recommend_deployment`: $0.25 USDC: recommend what to buy or run from bounded StackBench fit, performance, confidence, evidence, caveats, and economics only when supported.
- `search_evidence`: $0.00 free search of bounded public StackBench benchmark and failure evidence; use this for evidence-only requests.

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.