mcpbeat

Spikesh MCP Server

io.usefulapi/spikesh
answering

Spikesh is answering right now. Last checked 7 min ago. It exposes 16 tools. Last commit 1 Aug 2026.

Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.

Uptime history 40 hours of history · worst hour 0%
40 hours agonow
30.8%
Uptime 24h
28 of 91 checks
16
Tools
read from the server
174 ms
Response time
average over 24h
0
Stars
last commit 1 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add spikesh --transport http https://spikesh.usefulapi.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "spikesh": {
      "url": "https://spikesh.usefulapi.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.spikesh]
url = "https://spikesh.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "spikesh": {
      "url": "https://spikesh.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "spikesh": {
      "url": "https://spikesh.usefulapi.io/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

spike
spike_acknowledge_incidents
ACKNOWLEDGES one or more incidents — this CHANGES live incident state (stops escalation and marks them as being worked on). Spike: POST /incidents/acknowledge with {ids:[...]}.
spike_get_escalation
Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
spike_get_incident
Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
spike_get_incident_activity_log
Get the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counterId}/activity-log (team-scoped).
spike_get_on_call
Get one on-call schedule by id — {oncall:{_id, name, timezone, teams, users, activeShift, renderedShifts}}. `from` optionally sets the window start for rendered shifts. Spike: GET /on-calls/{oncallId} (team-scoped).
spike_get_service
Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).
spike_list_acknowledged_incidents
List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
spike_list_escalations
List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
spike_list_incidents
List incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timing. Spike: GET /incidents (team-scoped).
spike_list_on_calls
List a team's on-call schedules — {oncalls:[...]}. Each on-call has an id, name, timezone, and layers. Use the id with spike_get_on_call / spike_who_is_on_call_next. Spike: GET /on-calls (team-scoped).
spike_list_services
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
spike_list_teams
List all teams in the Spike.sh organization — {teams:[{_id, name, uid, private, org}]}. NOT team-scoped (no x-team-id needed). The `_id` values here are what you pass as `teamId` (x-team-id) to every other tool. Spike: GET /teams/get-all-teams.
spike_list_triggered_incidents
List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
spike_resolve_incidents
RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
spike_set_incident_priority
Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.
spike_who_is_on_call_next
Get the NEXT scheduled shift for an on-call schedule — {nextShift:{userId, startTimeInUTC, endTimeInUTC}} (or {} if none). Spike: GET /on-calls/{oncallId}/who-is-on-call-next (team-scoped).

Endpoints

URLTransportStateLatencyChecked
https://spikesh.usefulapi.io/mcp streamable-http answering 198 ms 7 min ago

Spikesh — questions

Answers built from our own checks of this server.

What can Spikesh do?
It exposes 16 tools, read directly from the server on our last check. Among them: spike_acknowledge_incidents, spike_get_escalation, spike_get_incident, spike_get_incident_activity_log, spike_get_on_call, spike_get_service and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Spikesh working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 28 of 91 checks got a reply (30.8%), average response time 174 ms. The bar chart above shows every period we have measured.
How do I connect Spikesh?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Spikesh need an API key?
No. Spikesh completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Spikesh?
It answers our handshake in 174 ms on average, which is faster than 68% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Spikesh open source?
Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.