All Quiet MCP by usefulapi
Server Details
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
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 11 tools
Most tools target distinct resources or actions (incidents, on-call overrides, teams, users, on-call status). However, get_incident and get_incident_markdown both retrieve the same incident with different renderings, and who_is_on_call and on_call_report both concern on-call state, which could cause slight misselection. Descriptions help clarify each use case.
All tools use a consistent allquiet_ prefix and snake_case, which is highly readable. The suffixes mostly follow verb_noun (create_incident, list_users), but on_call_report and who_is_on_call deviate as noun and question phrases. These are minor deviations that do not harm readability.
With 11 tools, the set is well within the typical 3–15 range for a focused integration. Each tool corresponds to a clear API operation and none appears redundant or trivial. The count is well matched to the incident/on-call domain.
Incident lifecycle is largely covered: create, get, get markdown, list, and update (severity/intent actions like acknowledge/resolve). Minor gaps exist for on-call overrides (no get, update, or delete) and teams/users (list only), but these are reasonable workarounds for a read/write incident-management surface.
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.
Read status-page status, services, incidents and metrics; create, update and publish incidents.
Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
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
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Incident.io to manage incidents, severities, and health checks via natural language. Provides endpoints for getting and creating incidents.1-
- 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.