MCP serverio.usefulapi/betterstack

Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.

UNRATEDActivestreamable-httpbetterstack.usefulapi.io

Overview

Score?

UNRATED 0.109

of what a free look can see, on 19 looks

Looks

last 10 hr ago

Tools

More info

URL

betterstack.usefulapi.io/mcp

streamable-http

Says it is

betterstack-mcp 1.0.1

protocol 2025-06-18

In the record since

32 days ago

Among servers18,413 with a card

0median 0.606 · this server 0.109 · highest on record 0.8561

Toolsfrom sha256:db97c1a3a5…5652ec

The tools this server lists, read out of the definition it returned
Tool	Schema
acknowledge_incident Acknowledge an ongoing incident, signalling that someone is looking into it (stops further escalation). Idempotent-ish: acknowledging an already-acknowledged incident returns HTTP	input · no output
get_incident Get a single incident by id, including cause, status, timeline timestamps (started/acknowledged/resolved), who acknowledged/resolved it, and the related monitor. Uptime API: GET /a	input · no output
get_monitor Get a single monitor by id, including current status, last_checked_at, SSL/HTTP settings, regions, and alerting configuration. Uptime API: GET /api/v2/monitors/{id}.	input · no output
list_heartbeats List heartbeats (cron/background-job monitors that expect a periodic ping), with period, grace, and status (up/down/paused/pending). Uptime API: GET /api/v2/heartbeats.	input · no output
list_incidents List incidents (alerts triggered by monitors/heartbeats), filterable by date range, monitor, and acknowledged/resolved state. Each incident carries cause, started_at, acknowledged_	input · no output
list_monitors List uptime monitors with their status (up/down/paused/pending/maintenance/validating), check frequency, and alert settings. Good first call to discover what is being monitored. Up	input · no output
list_on_call List 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.	input · no output
list_status_pages List public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.	input · no output
resolve_incident Resolve an ongoing incident, marking it as handled/closed. Idempotent-ish: resolving an already-resolved incident returns HTTP 409. Uptime API: POST /api/v3/incidents/{id}/resolve.	input · no output

Verify it yourselfnpx teppi-check https://betterstack.usefulapi.io/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M1FZ2PHQ0A7V7BG5DZDWD5F4