_ registry / mcp streamable-http · checked 11h ago

spikesh-mcp

https://spikesh.usefulapi.io

Registry code: a2dcd02ee646e7ad

api record

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

from a public catalogue that lists it, not from the operator

endpoint: https://spikesh.usefulapi.io/mcp
protocol: streamable-http ·2025-06-18
authentication: bearer
public key: none — nobody has proven they own this listing
karma: 0 · newcomer

reachable

live

uptime, 30 days

100%

90 days 100%· all time 100%

latency

350ms

last good check

priced tools

of 16 tools

_ answered our checks, 90 days 1 checks · signed record

2026-09-28 09:19 unknown → live

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts

distinct, expensive to fake

calls served

successful, last 30 days

_ what it can do 16 tools

16 never probed 0 of 16 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

spike_list_incidents unknown never probed

List incidents for a team — {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timing. Spike: GET /incidents (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 9007199254740991,
      "minimum": 1,
      "description": "1-based page number for pagination."
    },
    "teamId": {
      "type": "string",
      "description": "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."
    },
    "perPage": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Results per page."
    }
  }
}

arguments 22 lines

spike_list_triggered_incidents unknown never probed

List currently TRIGGERED (open, unacknowledged) incidents for a team — the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    }
  }
}

arguments 10 lines

spike_list_acknowledged_incidents unknown never probed

List currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    }
  }
}

arguments 10 lines

spike_get_incident unknown never probed

Get a single incident's full detail by its counterId — {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "counterId"
  ],
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    },
    "counterId": {
      "type": "string",
      "description": "The incident's counterId (its human-facing incident number/id)."
    }
  }
}

arguments 17 lines

spike_get_incident_activity_log unknown never probed

Get the chronological activity log for an incident — {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counterId}/activity-log (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "counterId"
  ],
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    },
    "counterId": {
      "type": "string",
      "description": "The incident's counterId."
    }
  }
}

arguments 17 lines

spike_list_on_calls unknown never probed

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    }
  }
}

arguments 10 lines

spike_get_on_call unknown never probed

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "oncallId"
  ],
  "properties": {
    "from": {
      "type": "string",
      "description": "ISO timestamp to render upcoming shifts from (e.g. \"2026-07-19T00:00:00Z\")."
    },
    "teamId": {
      "type": "string",
      "description": "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."
    },
    "oncallId": {
      "type": "string",
      "description": "The on-call schedule's id (from spike_list_on_calls)."
    }
  }
}

arguments 21 lines

spike_who_is_on_call_next unknown never probed

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "oncallId"
  ],
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    },
    "oncallId": {
      "type": "string",
      "description": "The on-call schedule's id."
    }
  }
}

arguments 17 lines

spike_list_escalations unknown never probed

List a team's escalation policies — {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    }
  }
}

arguments 10 lines

spike_get_escalation unknown never probed

Get one escalation policy by id — {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "escalationId"
  ],
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    },
    "escalationId": {
      "type": "string",
      "description": "The escalation policy's _id (from spike_list_escalations)."
    }
  }
}

arguments 17 lines

spike_get_service unknown never probed

Get one service by its counterId — {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "counterId"
  ],
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    },
    "counterId": {
      "type": "string",
      "description": "The service's counterId (from spike_list_services)."
    }
  }
}

arguments 17 lines

spike_acknowledge_incidents unknown never probed

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

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ids"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Incident ids (the incident `_id` values) to acknowledge."
    },
    "teamId": {
      "type": "string",
      "description": "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."
    }
  }
}

arguments 21 lines

spike_resolve_incidents unknown never probed

RESOLVES (closes) one or more incidents — this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ids"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Incident ids (the incident `_id` values) to resolve."
    },
    "teamId": {
      "type": "string",
      "description": "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."
    }
  }
}

arguments 21 lines

spike_set_incident_priority unknown never probed

Sets the PRIORITY (p1..p5) on one or more incidents — this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "ids",
    "priority"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Incident ids (the incident `_id` values) to update."
    },
    "teamId": {
      "type": "string",
      "description": "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."
    },
    "priority": {
      "enum": [
        "p1",
        "p2",
        "p3",
        "p4",
        "p5"
      ],
      "type": "string",
      "description": "Priority level: p1 (highest) .. p5 (lowest)."
    }
  }
}

arguments 33 lines

spike_list_teams unknown never probed
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.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

spike_list_services unknown never probed

List a team's services — {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "teamId": {
      "type": "string",
      "description": "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."
    }
  }
}

arguments 10 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/a2dcd02ee646e7ad/badge.svg)](https://brick.blue/agent/a2dcd02ee646e7ad)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know

card completeness

100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on usefulapi.io 23 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

zendesk.usefulapi.io zendesk-mcp mcp · 19 tools
recharge.usefulapi.io recharge-mcp mcp · 15 tools
emailoctopus.usefulapi.io emailoctopus-mcp mcp · 13 tools
memberful.usefulapi.io memberful-mcp mcp · 12 tools
statuspal.usefulapi.io statuspal-mcp mcp · 11 tools
mixpanel.usefulapi.io mixpanel-mcp mcp · 7 tools
speechmatics.usefulapi.io speechmatics-mcp mcp · 7 tools
maxmind-minfraud.usefulapi.io maxmind-minfraud-mcp mcp · 4 tools

15 more sit on this domain. All of them.