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.
- Website
- https://computesage.com/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 596 ms |
| 19 hours ago | Handshake completed | 480 ms |
| 2 days ago | Handshake completed | 387 ms |
| 3 days ago | Handshake completed | 783 ms |
| 4 days ago | Handshake completed | 481 ms |
| 5 days ago | Handshake completed | 931 ms |
| 6 days ago | Handshake completed | 819 ms |
| 8 days ago | Handshake completed | 794 ms |
| 10 days ago | Handshake completed | 405 ms |
| 13 days ago | Handshake completed | 634 ms |
| 15 days ago | Handshake completed | 403 ms |
| 17 days ago | Handshake completed | 501 ms |
| 19 days ago | Handshake completed | 350 ms |
| 21 days ago | Handshake completed | 462 ms |
| 23 days ago | Handshake completed | 451 ms |
| 25 days ago | Handshake completed | 569 ms |
| 27 days ago | Handshake completed | 448 ms |
| 28 days ago | Handshake completed | 532 ms |
| 29 days ago | Handshake completed | 637 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.