io.usefulapi/spikesh
REMOTE · SPIKESH.USEFULAPI.IO · SCANNED SEP 20
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Available components
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1832 tokens (~114/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/spikesh MCP server?
io.usefulapi/spikesh 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'
{
"mcpServers": {
"io-usefulapi-spikesh": {
"url": "https://spikesh.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-spikesh": {
"type": "http",
"url": "https://spikesh.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-spikesh] url = "https://spikesh.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-spikesh": {
"type": "remote",
"url": "https://spikesh.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-spikesh --url 'https://spikesh.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-spikesh:
url: "https://spikesh.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-spikesh": {
"Transport": "http",
"Url": "https://spikesh.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-spikesh -t streamable-http -u 'https://spikesh.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-spikesh": {
"type": "http",
"url": "https://spikesh.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Sept 26 +58
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 1 Sept 26 −45
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- 31 Aug 26 +45
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (spike_acknowledge_incidents) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 30 Aug 26 −45
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 28 Aug 26 −13
- Authorization: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 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 | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7de0a243e73ce3320e13a9c89f68272b |
| SANs: usefulapi.io, spikesh.usefulapi.io, *.spikesh.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 | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://spikesh.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://spikesh.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://spikesh.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://spikesh.usefulapi.io/mcp |
| Authorisation server | https://spikesh.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://spikesh.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/spikesh MCP server?
io.usefulapi/spikesh is an MCP server 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 io.usefulapi/spikesh MCP server safe to use?
io.usefulapi/spikesh scores 86 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 io.usefulapi/spikesh MCP server expose?
io.usefulapi/spikesh 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 io.usefulapi/spikesh MCP server require authentication?
Yes. io.usefulapi/spikesh asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/spikesh MCP server still maintained?
io.usefulapi/spikesh is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.