Spike.sh MCP by usefulapi
REMOTE · SPIKESH.USEFULAPI.IO
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Available components
Last scanned (21 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “acknowledge_or_resolve_incidents_and_set_priority” functional
- New prompt “check_escalation_policies_and_services” functional
- New prompt “find_who_is_on_call_next” functional
- New prompt “review_an_incident_and_its_activity_log” functional
- New prompt “see_which_incidents_are_open_and_unacknowledged” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.1 → 1.21.3 functional
- Server version: 1.21.0 → 1.21.1 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://spikesh.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of spikesh.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spikesh.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/spikesh/ |
| http (plaintext) | http://spikesh.usefulapi.io/mcp | Inconclusive | 302 | http://spikesh.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
spike_acknowledge_incidents Acknowledge incidents ~121
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:[...]}.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Incident ids (the incident `_id` values) to acknowledge. |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_get_escalation Get escalation policy ~118
Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| escalationId | string | yes | The escalation policy's _id (from spike_list_escalations). |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_get_incident Get incident ~116
Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| counterId | string | yes | The incident's counterId (its human-facing incident number/id). |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_get_incident_activity_log Get incident activity log ~114
Get the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counterId}/activity-log (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| counterId | string | yes | The incident's counterId. |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_get_on_call Get on-call schedule ~169
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).
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO timestamp to render upcoming shifts from (e.g. "2026-07-19T00:00:00Z"). |
| oncallId | string | yes | The on-call schedule's id (from spike_list_on_calls). |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_get_service Get service ~112
Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| counterId | string | yes | The service's counterId (from spike_list_services). |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_list_acknowledged_incidents List acknowledged incidents ~94
List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_list_escalations List escalation policies ~96
List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_list_incidents List incidents ~129
List incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timing. Spike: GET /incidents (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number for pagination. |
| perPage | integer | – | Results per page. |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_list_on_calls List on-call schedules ~112
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).
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_list_services List services ~93
List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_list_teams List teams ~81
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
spike_list_triggered_incidents List triggered incidents ~97
List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
| Name | Type | Req | Description |
|---|---|---|---|
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_resolve_incidents Resolve incidents ~114
RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Incident ids (the incident `_id` values) to resolve. |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_set_incident_priority Set incident priority ~136
Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | Incident ids (the incident `_id` values) to update. |
| priority | string | yes | Priority level: p1 (highest) .. p5 (lowest). |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
spike_who_is_on_call_next Who is on call next ~130
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).
| Name | Type | Req | Description |
|---|---|---|---|
| oncallId | string | yes | The on-call schedule's id. |
| teamId | string | – | The 24-char hex team _id to scope this request to (x-team-id). Omit to use the configured default (SPIKE_TEAM_ID). List ids with spike_list_teams. |
No output schema declared.
No examples provided.
How do I install the Spike.sh MCP by usefulapi server?
Spike.sh MCP by usefulapi is a hosted endpoint at https://spikesh.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · spikesh.usefulapi.io
claude mcp add --transport http io-usefulapi-spikesh 'https://spikesh.usefulapi.io/mcp'
What is the Spike.sh MCP by usefulapi server?
Spike.sh MCP by usefulapi is listed in the public MCP registry as io.usefulapi/spikesh. Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority. This page covers its hosted endpoint (https://spikesh.usefulapi.io/mcp).
Is the Spike.sh MCP by usefulapi server safe to use?
Spike.sh MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Spike.sh MCP by usefulapi server expose?
Spike.sh MCP by usefulapi exposes 16 tools: spike_list_teams, spike_list_incidents, spike_list_triggered_incidents, spike_list_acknowledged_incidents, spike_get_incident, and 11 more. Their descriptions and schemas cost roughly 1,832 tokens of context every time the server is loaded.
Does the Spike.sh MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Spike.sh MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Spike.sh MCP by usefulapi server still maintained?
Spike.sh MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.