io.usefulapi/spikesh

up checked 2026-11-11T14:37:17.481Z

Unclaimed · Unverified

Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.

Publisher-provided title

Spike.sh MCP by usefulapi

Publisher-provided description

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

Summary by lookupd

Reads incidents, on-call schedules, escalation policies and services, and can acknowledge, resolve or reprioritize incidents on Spike.sh.

Install

Claude Code, remote (streamable-http)

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

Codex, remote (streamable-http)

codex mcp add spikesh --url https://spikesh.usefulapi.io/mcp

Cursor, remote (streamable-http) → .cursor/mcp.json

{
  "mcpServers": {
    "spikesh": {
      "url": "https://spikesh.usefulapi.io/mcp"
    }
  }
}

Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.

Tools (16 tools)

Publisher-provided text

• 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 yo
• spike_list_incidents List incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timi
• 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-scop
• spike_get_incident_activity_log Get the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counter
• 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_
• 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
• 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-i
• 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).
• 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 w
• 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}.

Details

• Version: 1.37.3
• Transports: streamable-http
• Uptime (7 days): 100%
• Median latency: 337 ms
• First indexed: 2026-11-01T10:06:15.779Z
• Last seen in registry: 2026-11-11T00:17:34.405Z
• Repository: https://github.com/m190/usefulapi-mcp
• Website: https://usefulapi.io/spikesh/

Badge for your README

Shows this live status and links here; updates hourly.

[![lookupd status](https://lookupd.com/badge/io.usefulapi/spikesh.svg)](https://lookupd.com/servers/io.usefulapi/spikesh)

• 62071 servers
• Last crawl: 2026-11-11T16:17:25.167Z
• API base: https://api.lookupd.com
• MCP URL: https://api.lookupd.com/mcp