Better Stack MCP by usefulapi
Server Details
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve 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 9 tools
Each tool targets a distinct resource plus action: list vs get for monitors and incidents, plus separate heartbeat, on-call, and status page listings. The two mutating tools (acknowledge vs resolve) are clearly differentiated by intent and endpoint, so an agent can pick the right one without guessing.
Every tool follows the same betterstack_verb_noun snake_case pattern (list_monitors, get_incident, acknowledge_incident). No mixed conventions or vague verbs anywhere in the set.
Nine tools is well within the ideal range and each one maps to a concrete Better Stack Uptime endpoint. Nothing looks redundant or padded; the surface is deliberately scoped to monitoring, incidents, and on-call awareness.
The set is read-heavy with only two lifecycle actions (acknowledge/resolve), so agents cannot create, mute, update, or pause monitors, heartbeats, or status pages. There is also an asymmetry: monitors get both list and get, but heartbeats, status pages, and on-call have only list, leaving dead ends for drilling into a specific heartbeat or schedule.
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 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.
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).-- 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

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 gradedqualityCmaintenanceEnables checking current and upcoming on-call schedules, creating and reviewing agent incidents, and retrieving response-time, resolution-time, and SLA compliance metrics.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.