ComputeSage StackBench MCP Server

by computesage Your server? Claim it

answering

ComputeSage StackBench is answering right now. Last checked moments ago. It exposes 5 tools.

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

Uptime history 48 days of history · worst day 93%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

431 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 31 August 2026. No other catalogue keeps this.

31 Aug 5 tool descriptions were rewritten check_deployment_fit, generate_launch_config, predict_performance and 2 more

Nothing serious here today

Today is the operative word: we check ComputeSage StackBench every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "stackbench": {
      "url": "https://mcp.computesage.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.stackbench]
url = "https://mcp.computesage.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "stackbench": {
      "url": "https://mcp.computesage.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "stackbench": {
      "url": "https://mcp.computesage.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

deployment

check_deployment_fit

$0.01 USDC on Base mainnet: check model/configuration fit against bounded StackBench capacity evidence.

evidence

search_evidence

$0.00 free search of bounded public StackBench benchmark and failure evidence; use this for evidence-only requests.

generate

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

predict_performance

$0.05 USDC: predict configuration throughput, memory, and power from bounded StackBench evidence with confidence, missing metrics, and caveats.

recommend

recommend_deployment

$0.25 USDC: recommend what to buy or run from bounded StackBench fit, performance, confidence, evidence, caveats, and economics only when supported.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.computesage.com/mcp	streamable-http	answering	470 ms	0 min ago

Alternatives to ComputeSage StackBench

same job, measured the same way

Bim

by makata

Design-review threads, comments, reactions and deployments from Bim. Sign in with Google.

answering

InsForge

by insforge

MCP server for InsForge BaaS — database, storage, edge functions, and deployments

286 installs/wk answering

ChimeraForge

by sahil170595

Local-first LLM deployment planner: GPU/VRAM sizing, cost and latency, with provenance

5 121 installs/wk local only

MCP Agent Health Reporter

by aos-standard

Advisory AOS agent health scan before deployment (manifest, services, immune loop, evidence).

107 installs/wk local only

Cerebrium Docs

by cerebrium

Search the Cerebrium docs: deployment, cerebrium.toml, hardware, endpoints. Also sends feedback.

3 tools answering

Levelfour MCP

by levelfour

Cloud cost visibility and savings recommendations grounded in your actual AWS, GCP and Azure bill.

answering

Deploy to Agents

by deploytoagents

Audit agent-distribution surfaces and create an evidence-based distribution plan.

4 tools answering

Create Starter

by starter-series

Scaffold Starter Series projects and check release, deployment, security, and agent instructions.

43 installs/wk local only

ComputeSage StackBench — questions

Answers built from our own checks of this server.

What can ComputeSage StackBench do?

It exposes 5 tools, read directly from the server on our last check. Among them: check_deployment_fit, generate_launch_config, predict_performance, recommend_deployment, search_evidence. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is ComputeSage StackBench working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 431 ms. The bar chart above shows every period we have measured.

How do I connect ComputeSage StackBench?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does ComputeSage StackBench need an API key?

No. ComputeSage StackBench completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is ComputeSage StackBench?

It answers our handshake in 431 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.