Remote MCP · Endpoint
SigRank — AI Operator Benchmarking MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://signalaf.com/api/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- com.signalaf/sigrank
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- SigRank benchmark MCP: cascade metrics, leaderboard, operator profiles, simulation, diagnostics.
- Website
- https://signalaf.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Handshake completed | 1.30 s |
| 2 days ago | Handshake completed | 582 ms |
| 3 days ago | Handshake completed | 348 ms |
| 4 days ago | Handshake completed | 647 ms |
| 5 days ago | Handshake completed | 336 ms |
| 6 days ago | Handshake completed | 342 ms |
| 9 days ago | Handshake completed | 654 ms |
| 12 days ago | Handshake completed | 366 ms |
| 14 days ago | Handshake completed | 711 ms |
| 16 days ago | Handshake completed | 317 ms |
| 18 days ago | Handshake completed | 277 ms |
| 20 days ago | Handshake completed | 302 ms |
| 22 days ago | Handshake completed | 406 ms |
| 24 days ago | Handshake completed | 655 ms |
| 26 days ago | Handshake completed | 667 ms |
| 27 days ago | Handshake completed | 1.14 s |
| 28 days ago | Handshake completed | 282 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.
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 SigRank — AI Operator Benchmarking and makes no claim about it beyond what these checks measured.