io.usefulapi/betterstack
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Better Stack MCP by usefulapi
Publisher-provided description
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Summary by lookupd
Lists and inspects uptime monitors, heartbeats, incidents, on-call schedules and status pages, and can acknowledge or resolve incidents.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http betterstack https://betterstack.usefulapi.io/mcp
Codex, remote (streamable-http)
codex mcp add betterstack --url https://betterstack.usefulapi.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"betterstack": {
"url": "https://betterstack.usefulapi.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (9 tools)
Publisher-provided text
betterstack_list_monitorsList uptime monitors with their status (up/down/paused/pending/maintenance/validating), check frequency, and alert settings. Good first call to discover what isbetterstack_get_monitorGet a single monitor by id, including current status, last_checked_at, SSL/HTTP settings, regions, and alerting configuration. Uptime API: GET /api/v2/monitors/betterstack_list_incidentsList incidents (alerts triggered by monitors/heartbeats), filterable by date range, monitor, and acknowledged/resolved state. Each incident carries cause, startbetterstack_get_incidentGet a single incident by id, including cause, status, timeline timestamps (started/acknowledged/resolved), who acknowledged/resolved it, and the related monitorbetterstack_list_heartbeatsList heartbeats (cron/background-job monitors that expect a periodic ping), with period, grace, and status (up/down/paused/pending). Uptime API: GET /api/v2/heabetterstack_list_on_callList on-call calendars/schedules and the users currently on call for escalation. Useful to see who gets paged. Uptime API: GET /api/v2/on-calls.betterstack_list_status_pagesList public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.betterstack_acknowledge_incidentAcknowledge an ongoing incident, signalling that someone is looking into it (stops further escalation). Idempotent-ish: acknowledging an already-acknowledged inbetterstack_resolve_incidentResolve an ongoing incident, marking it as handled/closed. Idempotent-ish: resolving an already-resolved incident returns HTTP 409. Uptime API: POST /api/v3/inc
Details
- Version: 1.38.3
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 559 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/betterstack/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.usefulapi/betterstack)
- 62033 servers
- Last crawl: 2026-11-11T15:38:39.561Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp