Developer · Remote MCP server
ComputeSage StackBench
GPU and LLM inference benchmarks, hardware evidence, deployment recommendations, and launch configs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.computesage/stackbench- Version
- 0.2.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-08-29
- Updated
- 2026-08-29
- Publisher
- com.computesage
- Namespace
- Namespace verified by the MCP Registry via the domain computesage.com · how
- Website
- computesage.com/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.computesage.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- com.computesage/stackbench 0.2.1 · protocol 2025-06-18
- Tools discovered
- 5:
search_evidence,check_deployment_fit,predict_performance,recommend_deployment,generate_launch_config - Checked on
- 2026-10-05
How to connect ComputeSage StackBench
ComputeSage StackBench is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.computesage.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| CompletionKitPrompt evals over MCP: run a prompt on your dataset, score each output 1-5 with an LLM judge. | Remote · HTTPLive check: ✓ handshake |
| ComposerGive your AI coding agent an architecture canvas to design and evolve diagrams. | Local · stdio |
| Computer Use OmniA 1:1 replica of Claude Desktop's computer-use tool surface, for Windows and the Claude Code CLI. | Local · stdio |
| Computer-Use Agents APIRun and manage H Company's Computer-Use Agents from any MCP client. | Remote · HTTPLive check: ✓ handshake |
| Compuute MCP Security ScannerScan any public GitHub MCP-server repo for security issues. 37 MCP-specific L1 rules, 8 languages. | Remote · HTTPLive check: ✓ handshake |
| ConariumGoverned database access for AI assistants: masking, signed receipts, coverage reconciliation. | Local · stdio |
| ConcessioSearch 22,000+ infrastructure concessions: expiries, ownership, clauses, tenders. API key required. | Remote · SSELive check: ✓ SSE reachable |
| Concord MCPCross-harness communication and shared work-state for AI coding agents. | Local · stdio |