Spike.sh MCP by usefulapi

Install

Pick the AI app you use, then copy the settings.

Passed 4/4 checks · What you ask goes through the maker’s server (spikesh.usefulapi.io) · ✓ Commands checked Nov 13, 2026

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

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

{
  "servers": {
    "spikesh": {
      "type": "http",
      "url": "https://spikesh.usefulapi.io/mcp"
    }
  }
}

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

What it can do

Tool names and descriptions exactly as the server reported them on Nov 14, 2026. The maker wrote them, not us; we show them as plain 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 you pass as `teamId` (x-team-id) to every other tool. Spike: GET /teams/get-all-teams.

• 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_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).

• 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}.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 15, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• ✓ Pass

  Still maintained

  Code last changed yesterday

• – Not applicable

  Has a licence

  Not applicable: a cloud server run by the owner of usefulapi.io; you don't run code from the repo

• ✓ Pass

  Endpoint responds

  Responded in 10 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 16 tool descriptions and found no hidden instructions to the AI

What we check → · JSON

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

• More stars than 0% of the other 19903 servers in this category
• Published to the registry more recently than 97% of the other 19903 servers in this category
• Basic checks equal to or better than 100% of the other 19903 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

by koala73·Widely used·★ 90.7K·Updated yesterday

Runs in the cloud✓ service owner · worldmonitor.app

How to connect

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQ·Widely used·★ 9.3K·Updated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

How to connect

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleer·Widely used·★ 23.8K Stars for the whole repo·Updated 26 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

How to connect

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AI·Growing·★ 5.8K·Updated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

How to connect

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucom·Widely used·★ 5.1K·Updated 4 months ago

Runs in the cloud✓ service owner · jitsu.com

How to connect

• World Monitor — Runs in the cloud, nothing to install · No key needed
• openstatus — Runs in the cloud, nothing to install · No key needed
• Oh My Posh Validator — Runs in the cloud, nothing to install · No key needed
• Strata — Runs in the cloud, nothing to install · No key needed
• Jitsu — Runs in the cloud, nothing to install · No key needed

README from the maker

{