Remote MCP · Endpoint

ComputeSage StackBench MCP server

No. ComputeSage StackBench answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.computesage.com/mcp

The last check completed an MCP handshake.

Registry name
com.computesage/stackbench
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
596 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
GPU and LLM inference benchmarks, hardware evidence, deployment recommendations, and launch configs.
Listing
From the official MCP registry (active).
Recent checks of ComputeSage StackBench
CheckedResultHandshake
1 hour agoHandshake completed596 ms
19 hours agoHandshake completed480 ms
2 days agoHandshake completed387 ms
3 days agoHandshake completed783 ms
4 days agoHandshake completed481 ms
5 days agoHandshake completed931 ms
6 days agoHandshake completed819 ms
8 days agoHandshake completed794 ms
10 days agoHandshake completed405 ms
13 days agoHandshake completed634 ms
15 days agoHandshake completed403 ms
17 days agoHandshake completed501 ms
19 days agoHandshake completed350 ms
21 days agoHandshake completed462 ms
23 days agoHandshake completed451 ms
25 days agoHandshake completed569 ms
27 days agoHandshake completed448 ms
28 days agoHandshake completed532 ms
29 days agoHandshake completed637 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 responding of 30.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with ComputeSage StackBench and makes no claim about it beyond what these checks measured.