Spike.sh MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

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

Deletes · 3Changes · 1

Compare Registry entry

16 tools: 3 can delete or cancel things, 1 change things and 12 only read.

Scanned Oct 21, 2026

Deletes or cancels3Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things1Claude Code: ask: see these tools
Only reads12Claude Code: allow: see these tools

3 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcp

Findings

Matches of fixed checks, with the text they matched.

3 warn

Warnspike_list_teams
The description contains "every other tool", wording about other tools or servers.
Matched text
description: "...hat you pass as `teamId` (x-team-id) to every other tool. Spike: GET /teams/get-all-teams."
What this check looks for
Warnspike_who_is_on_call_next
The server marks "spike_who_is_on_call_next" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
Matched text
annotations: {"readOnlyHint":true}; The name "spike_who_is_on_call_next" says "call": a word for a change.
What this check looks for
Warnspike_resolve_incidents
The server marks "spike_resolve_incidents" destructive (destructiveHint: true), and its name says "resolve", a word for reading.
Matched text
annotations: {"destructiveHint":true}; The name "spike_resolve_incidents" says "resolve": a word for reading.
What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

16 tools

Deletes or cancels 3Removes, cancels or revokes something.Claude Code: deny

spike_acknowledge_incidentsACKNOWLEDGES one or more incidents — this CHANGES live incident state (stops escalation and marks them as being worked on).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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:[...]}.
Annotations the server declares
- title: Acknowledge incidents
- destructiveHint: true
spike_resolve_incidentsRESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done.1 finding
Why it is in this group
- The name "spike_resolve_incidents" says "resolve": a word for reading.
- The server marks it destructive (destructiveHint: true).
Findings
- Warn
  The server marks "spike_resolve_incidents" destructive (destructiveHint: true), and its name says "resolve", a word for reading.
  Matched text
  annotations: {"destructiveHint":true}; The name "spike_resolve_incidents" says "resolve": a word for reading.
  What this check looks for
Description, as the server wrote it
RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
Annotations the server declares
- title: Resolve incidents
- destructiveHint: true
spike_set_incident_prioritySets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state.No findings
Why it is in this group
- The name "spike_set_incident_priority" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.
Annotations the server declares
- title: Set incident priority
- destructiveHint: true

Changes things 1Creates or changes something that can be changed back.Claude Code: ask

spike_who_is_on_call_nextGet the NEXT scheduled shift for an on-call schedule — {nextShift:{userId, startTimeInUTC, endTimeInUTC}} (or {} if none).1 finding
Why it is in this group
- The name "spike_who_is_on_call_next" says "call": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
  The server marks "spike_who_is_on_call_next" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
  Matched text
  annotations: {"readOnlyHint":true}; The name "spike_who_is_on_call_next" says "call": a word for a change.
  What this check looks for
Description, as the server wrote it
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).
Annotations the server declares
- title: Who is on call next
- readOnlyHint: true

Only reads 12Looks things up and changes nothing.Claude Code: allow

spike_get_escalationGet one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}.No findings
Why it is in this group
- The name "spike_get_escalation" says "get": a word for reading.
Description, as the server wrote it
Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
Annotations the server declares
- title: Get escalation policy
- readOnlyHint: true
spike_get_incidentGet a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}.No findings
Why it is in this group
- The name "spike_get_incident" says "get": a word for reading.
Description, as the server wrote it
Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
Annotations the server declares
- title: Get incident
- readOnlyHint: true
spike_get_incident_activity_logGet the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when).No findings
Why it is in this group
- The name "spike_get_incident_activity_log" says "get": a word for reading.
Description, as the server wrote it
Get the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counterId}/activity-log (team-scoped).
Annotations the server declares
- title: Get incident activity log
- readOnlyHint: true
spike_get_on_callGet one on-call schedule by id — {oncall:{_id, name, timezone, teams, users, activeShift, renderedShifts}}.No findings
Why it is in this group
- The name "spike_get_on_call" says "get": a word for reading.
Description, as the server wrote it
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).
Annotations the server declares
- title: Get on-call schedule
- readOnlyHint: true
spike_get_serviceGet one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}.No findings
Why it is in this group
- The name "spike_get_service" says "get": a word for reading.
Description, as the server wrote it
Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).
Annotations the server declares
- title: Get service
- readOnlyHint: true
spike_list_acknowledged_incidentsList currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team.No findings
Why it is in this group
- The name "spike_list_acknowledged_incidents" says "list": a word for reading.
Description, as the server wrote it
List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
Annotations the server declares
- title: List acknowledged incidents
- readOnlyHint: true
spike_list_escalationsList a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}.No findings
Why it is in this group
- The name "spike_list_escalations" says "list": a word for reading.
Description, as the server wrote it
List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
Annotations the server declares
- title: List escalation policies
- readOnlyHint: true
spike_list_incidentsList incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}.No findings
Why it is in this group
- The name "spike_list_incidents" says "list": a word for reading.
Description, as the server wrote it
List incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timing. Spike: GET /incidents (team-scoped).
Annotations the server declares
- title: List incidents
- readOnlyHint: true
spike_list_on_callsList a team's on-call schedules — {oncalls:[...]}.No findings
Why it is in this group
- The name "spike_list_on_calls" says "list": a word for reading.
Description, as the server wrote it
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).
Annotations the server declares
- title: List on-call schedules
- readOnlyHint: true
spike_list_servicesList a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}.No findings
Why it is in this group
- The name "spike_list_services" says "list": a word for reading.
Description, as the server wrote it
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
Annotations the server declares
- title: List services
- readOnlyHint: true
spike_list_teamsList all teams in the Spike.sh organization — {teams:[{_id, name, uid, private, org}]}.1 finding
Why it is in this group
- The name "spike_list_teams" says "list": a word for reading.
Findings
- Warn
  The description contains "every other tool", wording about other tools or servers.
  Matched text
  description: "...hat you pass as `teamId` (x-team-id) to every other tool. Spike: GET /teams/get-all-teams."
  What this check looks for
Description, as the server wrote it
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.
Annotations the server declares
- title: List teams
- readOnlyHint: true
spike_list_triggered_incidentsList currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue.No findings
Why it is in this group
- The name "spike_list_triggered_incidents" says "list": a word for reading.
Description, as the server wrote it
List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
Annotations the server declares
- title: List triggered incidents
- readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.16.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__spikesh__spike_list_teams",
      "mcp__spikesh__spike_list_incidents",
      "mcp__spikesh__spike_list_triggered_incidents",
      "mcp__spikesh__spike_list_acknowledged_incidents",
      "mcp__spikesh__spike_get_incident",
      "mcp__spikesh__spike_get_incident_activity_log",
      "mcp__spikesh__spike_list_on_calls",
      "mcp__spikesh__spike_get_on_call",
      "mcp__spikesh__spike_list_escalations",
      "mcp__spikesh__spike_get_escalation",
      "mcp__spikesh__spike_list_services",
      "mcp__spikesh__spike_get_service"
    ],
    "ask": [
      "mcp__spikesh__spike_who_is_on_call_next"
    ],
    "deny": [
      "mcp__spikesh__spike_acknowledge_incidents",
      "mcp__spikesh__spike_resolve_incidents",
      "mcp__spikesh__spike_set_incident_priority"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as spikesh. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/spikesh/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing