Spike.sh MCP by usefulapi
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority
Reviews
No review yet. Used Spike.sh MCP by usefulapi? Be the first to help others choose.What it does
Spike.sh MCP by usefulapi is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 14h ago (live check)Hosted endpoint
https://spikesh.usefulapi.io/mcpstreamable-http
In Claude Code: claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"spikesh": {
"url": "https://spikesh.usefulapi.io/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 14h agoONLINE Spike.sh MCP by usefulapi answered an MCP connection on 16 Nov 2026 and introduced itself as spikesh-mcp 1.39.2 (MCP protocol 2025-06-18).
16 tools offered to AI assistants
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-tespike_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_triggered_incidents· List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (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_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_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_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_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).spike_list_escalations· List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).spike_get_escalation· Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).spike_list_services· List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
Show 4 more
spike_get_service· Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).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_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}.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Version | 1.40.0 | DECLARED | SRC-001 Official MCP Registry | 4m ago |
| Hosted endpoint | https://spikesh.usefulapi.io/mcp | DECLARED | SRC-001 Official MCP Registry | 4m ago |
| Website | https://usefulapi.io/spikesh/ | DECLARED | SRC-001 Official MCP Registry | 4m ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 4m ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 4m ago |
| Repository | https://github.com/m190/usefulapi-mcp | DECLARED | SRC-001 Official MCP Registry | 4m ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 4m ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 4m ago |
Change history
- VERSION16 Nov 20261.39.2 → 1.39.3
- VERSION14 Nov 20261.39.1 → 1.39.2
- VERSION13 Nov 20261.39.0 → 1.39.1
- VERSION13 Nov 20261.38.0 → 1.39.0
- VERSION11 Nov 20261.37.3 → 1.38.0
- VERSION11 Nov 20261.37.2 → 1.37.3
- VERSION10 Nov 20261.37.1 → 1.37.2
- VERSION10 Nov 20261.37.0 → 1.37.1
- VERSION10 Nov 20261.36.5 → 1.37.0
- VERSION07 Nov 20261.36.4 → 1.36.5
- VERSION07 Nov 20261.36.3 → 1.36.4
- VERSION07 Nov 20261.36.2 → 1.36.3
- VERSION06 Nov 20261.36.1 → 1.36.2
- VERSION06 Nov 20261.35.4 → 1.36.1
- VERSION06 Nov 20261.35.3 → 1.35.4
- VERSION05 Nov 20261.35.2 → 1.35.3
- VERSION05 Nov 20261.35.1 → 1.35.2
- VERSION03 Nov 20261.35.0 → 1.35.1
- VERSION03 Nov 20261.34.1 → 1.35.0
- VERSION03 Nov 20261.34.0 → 1.34.1
- VERSION02 Nov 20261.33.0 → 1.34.0
- VERSION31 Oct 20261.32.0 → 1.33.0
- VERSION31 Oct 20261.31.0 → 1.32.0
- VERSION31 Oct 20261.30.0 → 1.31.0
- VERSION31 Oct 20261.29.2 → 1.30.0
- VERSION30 Oct 20261.29.1 → 1.29.2
- VERSION30 Oct 20261.29.0 → 1.29.1
- VERSION29 Oct 20261.28.0 → 1.29.0
- VERSION29 Oct 20261.27.0 → 1.28.0
- VERSION28 Oct 20261.26.0 → 1.27.0
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Spike.sh MCP by usefulapi still online?
Free alerts · no account▲ 0Do you run Spike.sh MCP by usefulapi? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Spike.sh MCP by usefulapi
How do I connect Spike.sh MCP by usefulapi?
Use the hosted endpoint https://spikesh.usefulapi.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does Spike.sh MCP by usefulapi offer?
When Electra Index connected on 16 Nov 2026, it listed 16 tools: spike_list_teams, spike_list_incidents, spike_list_triggered_incidents, spike_list_acknowledged_incidents, spike_get_incident, spike_get_incident_activity_log, spike_list_on_calls, spike_get_on_call and more. The full list is in "Live check" above.
Is Spike.sh MCP by usefulapi online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 14h ago.