Sorry MCP by usefulapi
Server Details
Read status pages and incidents; make confirmed public changes and manage individual subscribers.
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 21 tools
Most tools are cleanly separated by resource and action, and the incident/maintenance split is explicitly explained as type=unplanned vs type=planned. The main blur is that sorryapp_update_notice can also append a timeline comment, overlapping with sorryapp_create_notice_update, and edit_notice_update vs update_notice use different verbs for the same underlying action.
All 21 tools use a uniform sorryapp_ prefix with snake_case verb_noun (create_/get_/list_/update_), which is highly predictable. The only deviation is sorryapp_edit_notice_update using 'edit' where every other mutation uses 'update'.
21 tools for pages, components, notices, updates, subscribers, templates, and timezones is defensible but sits in the heavy range, especially with four list tools for templates/timezones. A few tools (e.g. list_notice_templates, list_update_templates) add surface area for read-only metadata rather than core lifecycle operations.
The create/get/list/update path is covered for components, notices, and updates, and the write tools cover the core status-page workflow (open incident, post update, resolve). However, there is no delete anywhere (component, notice, notice update) and no way to update or remove a subscriber, so unsubscribe/cleanup workflows are dead ends; page-level create/update is also absent.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read status-page status, services, incidents and metrics; create, update and publish incidents.
Read pages, components, incidents and maintenances; create and update incidents in Statuspage.
Status pages and uptime monitoring: read status, monitors and incidents; open incidents.
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Related MCP Servers
FlicenseNot gradedqualityDmaintenanceLet agents read and manage your org’s independent monitors, incidents, status pages, and alerts (honest measured state, no false greens).-- AlicenseAqualityBmaintenanceEnables agents to inspect app status, uptime, response times, incidents, and certificate/domain expiry; set up and manage monitors and status pages; and draft incident updates through authenticated MCP tools.1133Functional Source , Version 1.1, MIT Future

Uptimy MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect uptime monitoring, incidents, status pages, alerts, dependencies, and reports. It also supports related changes such as opening incidents, posting updates, scheduling maintenance, adding monitors, and configuring alerts and reports.Apache 2.0- AlicenseNot gradedqualityBmaintenanceLets coding agents create and manage heartbeat, website, TCP, DNS, SSL certificate, and domain monitoring checks, and read check history, incidents, uptime, latency metrics, and dashboards.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.