spikesh

Tools

16 tools: 13 read-only, 0 change data, 3 high risk (delete, pay, send or run code).

No tool name points to sending messages.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 2,810 tokens of tool definitions and a 603 ms handshake.

• high riskspike_acknowledge_incidentsACKNOWLEDGES one or more incidents - this CHANGES live incident state (stops escalation and marks them as being worked on). Spike: POST /incidents/acknowledge with {ids:[...]}.
• high riskspike_resolve_incidentsRESOLVES (closes) one or more incidents - this CHANGES live incident state and marks them done. Spike: POST /incidents/resolve with {ids:[...]}.
• high riskspike_set_incident_prioritySets the PRIORITY (p1..p5) on one or more incidents - this CHANGES live incident state. Spike: POST /incidents/priority with {ids:[...], priority}.
• read-onlyspike_list_teamsList 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.
• read-onlyspike_list_incidentsList incidents for a team - {incidents:[...], totalIncidents, totalOpenIncidents, pagination}. Each incident carries title, status, priority, severity, and timing. Spike: GET /incidents (team-scoped).
• read-onlyspike_list_triggered_incidentsList currently TRIGGERED (open, unacknowledged) incidents for a team - the active fire-fighting queue. Spike: GET /incidents/triggered (team-scoped).
• read-onlyspike_list_acknowledged_incidentsList currently ACKNOWLEDGED (being worked on, not yet resolved) incidents for a team. Spike: GET /incidents/acknowledged (team-scoped).
• read-onlyspike_get_incidentGet a single incident's full detail by its counterId - {incident, duration, metadata, comments, repeatedIncidents}. Spike: GET /incidents/{counterId} (team-scoped).
• read-onlyspike_get_incident_activity_logGet the chronological activity log for an incident - {incident, activities:[...]} (who acknowledged/resolved/commented and when). Spike: GET /incidents/{counterId}/activity-log (team-scoped).
• read-onlyspike_list_on_callsList 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).
• read-onlyspike_get_on_callGet 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).
• read-onlyspike_who_is_on_call_nextGet 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).
• read-onlyspike_list_escalationsList a team's escalation policies - {totalEscalations, escalations:[{_id, name, teams, org}], pagination}. Spike: GET /escalations (team-scoped).
• read-onlyspike_get_escalationGet one escalation policy by id - {escalation, integrations:[...], isPinned, alertRules}. Spike: GET /escalations/{escalationId} (team-scoped).
• read-onlyspike_list_servicesList a team's services - {totalServices, services:[{_id, counterId, name, desc, teams, org}], pagination}. Spike: GET /services (team-scoped).
• read-onlyspike_get_serviceGet one service by its counterId - {service, org, openIncidentsCountForService, incidents, badgeURL}. Spike: GET /services/{counterId} (team-scoped).

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-04, 603 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-052026-10-04

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Bookings and appointments, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/spikesh.usefulapi.io/mcp.svg)](https://7it.co.il/7maps/s/spikesh.usefulapi.io/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=spikesh.usefulapi.io%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/spikesh.usefulapi.io/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/spikesh.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=spikesh.usefulapi.io%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.