Skip to content

ComputeSage StackBench

by computesage.com · remote · no sign-in to list tools · v0.2.1 · published by com.computesage

GPU and LLM inference benchmarks, hardware evidence, deployment recommendations, and launch configs.

Changes · 4

5 tools: 4 change things and 1 only read.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "generate_launch_config" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_launch_config" says "generate": a word for a change.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Changes things 4Claude Code: ask
  • check_deployment_fit$0.01 USDC on Base mainnet: check model/configuration fit against bounded StackBench capacity evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    $0.01 USDC on Base mainnet: check model/configuration fit against bounded StackBench capacity evidence.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • generate_launch_config$0.50 USDC: generate deterministic vLLM or llama.cpp launch templates from an exact StackBench recommendation without claiming a launch occurred.1 finding

    Why it is in this group

    • The name "generate_launch_config" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "generate_launch_config" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_launch_config" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    $0.50 USDC: generate deterministic vLLM or llama.cpp launch templates from an exact StackBench recommendation without claiming a launch occurred.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • predict_performance$0.05 USDC: predict configuration throughput, memory, and power from bounded StackBench evidence with confidence, missing metrics, and caveats.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    $0.05 USDC: predict configuration throughput, memory, and power from bounded StackBench evidence with confidence, missing metrics, and caveats.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • recommend_deployment$0.25 USDC: recommend what to buy or run from bounded StackBench fit, performance, confidence, evidence, caveats, and economics only when supported.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    $0.25 USDC: recommend what to buy or run from bounded StackBench fit, performance, confidence, evidence, caveats, and economics only when supported.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Claude Code: allow
  • search_evidence$0.00 free search of bounded public StackBench benchmark and failure evidence; use this for evidence-only requests.No findings

    Why it is in this group

    • The name "search_evidence" says "search": a word for reading.
    Description, as the server wrote it
    $0.00 free search of bounded public StackBench benchmark and failure evidence; use this for evidence-only requests.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__stackbench__search_evidence"
    ],
    "ask": [
      "mcp__stackbench__check_deployment_fit",
      "mcp__stackbench__predict_performance",
      "mcp__stackbench__recommend_deployment",
      "mcp__stackbench__generate_launch_config"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as stackbench. Review it before you use it.