Squadcast MCP by usefulapi
Server Details
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
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 has a distinct resource and action: incident actions (acknowledge, resolve, add note), incident reads (get, list, events, notes), and separate list/get operations for services, teams, users, schedules, squads, and escalation policies. The only potential confusion is between similar incident-related tools like get_incident and get_incident_events, but their descriptions make the boundaries clear.
All 16 tools follow the exact same squadcast_verb_noun snake_case pattern. There are no mixed conventions, vague verbs, or inconsistent casing.
16 tools is slightly above the ideal 3-15 range, but the set is well-scoped for an incident management and on-call integration. Each tool maps to a distinct resource or incident action, and none appear redundant.
The server covers incident read/action workflows (get, list, events, notes, acknowledge, resolve) and list/get coverage for core entities, but lacks create/update/delete operations for services, teams, users, schedules, escalation policies, and squads. It also omits incident creation or broader incident updates like reassignment, so it is suited for response workflows but not full lifecycle or admin management.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
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 status-page status, services, incidents and metrics; create, update and publish incidents.
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
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).-- AlicenseAqualityBmaintenanceEnables interaction with Jira Service Management Operations alerts and on-call schedules, including searching alerts, reading notes and activity logs, acknowledging, closing, annotating, adding responders, and querying current and next on-call rotations.28526 npm5Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.