Spike.sh MCP by usefulapi
io.usefulapi/spikeshusefulapi.iostreamable-httpv1.40.4Scanned
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
16 tools: 3 can delete or cancel things, 1 change things and 12 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 3 findings
The remote endpoint did not answer the last look. Remote posture
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 Radar 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 →What the Spike.sh MCP by usefulapi can do
The Spike.sh MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (3 tools: spike_acknowledge_incidents, spike_resolve_incidents and spike_set_incident_priority) and create or change data (1 tool: spike_who_is_on_call_next). 12 tools only read.
2 tools bring in text other people can write (spike_get_incident and spike_get_service).
The fixed checks matched 3 findings (tool-shadowing and annotation-conflict). Each one comes with the text it matched.
Last scanned Oct 25, 2026, version 1.40.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Deletes or cancels 3Claude 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.
What this check looks forMatched text
annotations: {"destructiveHint":true}; The name "spike_resolve_incidents" says "resolve": a word for reading.
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 1Claude 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".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "spike_who_is_on_call_next" says "call": a word for a change.
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 12Show 12 read-only tools
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}.Reads text others writeNo findings
Why it is in this group
- The name "spike_get_incident" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "comment": it reads comments, which other people can write.
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}.Reads text others writeNo findings
Why it is in this group
- The name "spike_get_service" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
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.
What this check looks forMatched text
description: "...hat you pass as `teamId` (x-team-id) to every other tool. Spike: GET /teams/get-all-teams."
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://spikesh.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://spikesh.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
- Warnspike_list_teams
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...hat you pass as `teamId` (x-team-id) to every other tool. Spike: GET /teams/get-all-teams."
The server marks "spike_who_is_on_call_next" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "spike_who_is_on_call_next" says "call": a word for a change.
The server marks "spike_resolve_incidents" destructive (destructiveHint: true), and its name says "resolve", a word for reading.
What this check looks forMatched text
annotations: {"destructiveHint":true}; The name "spike_resolve_incidents" says "resolve": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://spikesh.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://spikesh.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcpclaude mcp add --transport http spikesh https://spikesh.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as spikesh. Review it before you use it.
Capability tags behind 2 rules
- mcp__spikesh__spike_get_incident untrusted-input
- mcp__spikesh__spike_get_service untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/spikesh/verify?hash=d2586513d76228becb4fd0108fbfc8d81c1b478c521b7c1d36119f6c1039b37f" | jq -e '.changed == false'Pinned hash d2586513d762, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/spikesh/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/spikesh)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Spike.sh MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Spike.sh MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 16 tools, 4 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Spike.sh MCP by usefulapi delete data?
- Yes. 3 tools can delete, cancel or revoke something: spike_acknowledge_incidents, spike_resolve_incidents and spike_set_incident_priority.
Can the Spike.sh MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Spike.sh MCP by usefulapi have?
- 16 tools: 3 destructive, 1 write, 12 read. spike_acknowledge_incidents, spike_resolve_incidents, spike_set_incident_priority, spike_who_is_on_call_next, spike_list_teams, spike_list_incidents, spike_list_triggered_incidents, spike_list_acknowledged_incidents and 8 more.
Does the Spike.sh MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Spike.sh MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Spike.sh MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.