io.usefulapi/spikesh

REMOTE · SPIKESH.USEFULAPI.IO · SCANNED AUG 3

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

Available components

+4 this week 73 73 Trust /100

Trust breakdown (6 categories)

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 →

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 not yet verified: we couldn't determine whether a plaintext access path exists. 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 Usability75

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 Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · spikesh.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.io-usefulapi-spikesh]
url = "https://spikesh.usefulapi.io/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-spikesh": {
      "type": "remote",
      "url": "https://spikesh.usefulapi.io/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add io-usefulapi-spikesh --url https://spikesh.usefulapi.io/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  io-usefulapi-spikesh:
    url: "https://spikesh.usefulapi.io/mcp"

// mcp.json

{
  "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.

Changelog

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.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +57
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 12

First indexed and scored.

Show 7 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 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	19 Jul 2026	17 Oct 2026	ECDSA 256	ECDSA-SHA256	60dab39a5aa79285130df150c2f4a83f
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

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

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

MCP tools — 16 exposed · ~1,832 tokens

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.

Tool Tokens

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:[...]}.

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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 Output Examples

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

Input Output Examples

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:[...]}.

Input Output Examples

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

Input Output Examples

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

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	69
28 Jul	69
29 Jul	70
30 Jul	71
31 Jul	71
1 Aug	72
2 Aug	72
3 Aug	73