Remote MCP · Endpoint
Spike.sh MCP by usefulapi MCP server
No. Spike.sh MCP by usefulapi answered an MCP handshake 5 hours ago.
UpLast checked 5 hours ago
Server URL
https://spikesh.usefulapi.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.usefulapi/spikesh
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 232 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
- Repository
- https://github.com/m190/usefulapi-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 5 hours ago | Handshake completed | 232 ms |
| 2 days ago | Handshake completed | 246 ms |
| 4 days ago | Handshake completed | 259 ms |
| 5 days ago | Handshake completed | 182 ms |
| 7 days ago | Handshake completed | 185 ms |
| 8 days ago | Handshake completed | 316 ms |
| 9 days ago | Handshake completed | 292 ms |
| 12 days ago | Handshake completed | 210 ms |
| 13 days ago | Handshake completed | 177 ms |
| 15 days ago | Handshake completed | 286 ms |
| 16 days ago | Handshake completed | 163 ms |
| 17 days ago | Handshake completed | 123 ms |
| 18 days ago | Handshake completed | 311 ms |
| 19 days ago | Handshake completed | 152 ms |
| 20 days ago | Handshake completed | 200 ms |
| 21 days ago | Handshake completed | 276 ms |
| 22 days ago | Handshake completed | 356 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.
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 Spike.sh MCP by usefulapi and makes no claim about it beyond what these checks measured.