Spike.sh MCP by usefulapi
Server Details
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 16 tools
Each tool targets a distinct resource and action; the three incident listers (all, acknowledged, triggered) are clearly differentiated by their status filters in descriptions. On-call tools (list, get, next) and escalation/service read pairs are unambiguous.
Consistent snake_case with spike_ prefix and verb_noun pattern throughout. Only spike_who_is_on_call_next deviates slightly from the strict verb_noun convention but remains descriptive and predictable.
16 tools across five resources (incidents, on-calls, escalations, services, teams) is well-scoped; each tool earns its place. However, the total sits at the upper end of the ideal range (16-25 feels heavy per calibration).
Covers the incident response lifecycle (list, get, acknowledge, resolve, set priority) plus read access to on-call schedules, escalation policies, and services. Missing write operations such as adding comments or creating configurations are minor for an incident-response agent but present gaps.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
Read pages, components, incidents and maintenances; create and update incidents in Statuspage.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables PagerDuty incident response operations including listing incidents, acknowledging and resolving incidents, looking up on-call schedules, and listing services.MIT
- AlicenseNot gradedqualityCmaintenanceEnables checking current and upcoming on-call schedules, creating and reviewing agent incidents, and retrieving response-time, resolution-time, and SLA compliance metrics.MIT

StackWitnessofficial
FlicenseNot gradedqualityDmaintenanceLet agents read and manage your org’s independent monitors, incidents, status pages, and alerts (honest measured state, no false greens).-- AlicenseNot gradedqualityDmaintenanceThis server provides a full API interface for the Splunk On-Call (VictorOps) platform, allowing comprehensive interaction with incident management tools. It enables users to manage incidents, configure organizational structures, and view on-call schedules.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.