Remote MCP · Endpoint

Spike.sh MCP by usefulapi MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://spikesh.usefulapi.io/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.usefulapi/spikesh
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
16 tools
Uptime, last 30 days
50.0% from 18 checks
Described by its publisher as
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Website
https://usefulapi.io/spikesh/
Repository
https://github.com/m190/usefulapi-mcp
Listing
From the official MCP registry (active).
Recent checks of Spike.sh MCP by usefulapi
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed383 ms
17 days agoHandshake completed288 ms
19 days agoHandshake completed234 ms
21 days agoHandshake completed232 ms
23 days agoHandshake completed246 ms
25 days agoHandshake completed259 ms
26 days agoHandshake completed182 ms
28 days agoHandshake completed185 ms
29 days agoHandshake completed316 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 20 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.