Better Stack MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Better Stack MCP by usefulapi is answering right now. Last checked 11 min ago. It exposes 9 tools. Last commit 2 Nov 2026.

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

Uptime history 91 days of history · worst day 3%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

157 ms

Response time

average over 24h

Stars

last commit 2 Nov 2026

What changed 63

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 30 September 2026. No other catalogue keeps this.

2 Nov a tool changed version

31 Oct a tool changed version5 times that day

30 Oct a tool changed version2 times that day

29 Oct a tool changed version2 times that day

28 Oct a tool changed version2 times that day

27 Oct a tool changed version

25 Oct a tool changed version4 times that day

24 Oct a tool changed version3 times that day

23 Oct a tool changed version

22 Oct 9 tools appeared betterstack_acknowledge_incident, betterstack_get_incident, betterstack_get_monitor and 6 more

and 45 more, back to 30 September 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add betterstack --transport http https://betterstack.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://betterstack.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.betterstack]
url = "https://betterstack.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "betterstack": {
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "betterstack": {
      "type": "http",
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

betterstack

betterstack_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 409. Uptime API: POST /api/v3/incidents/{id}/acknowledge.

betterstack_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 /api/v3/incidents/{id}.

betterstack_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}.

betterstack_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.

betterstack_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_at, resolved_at. Uptime API: GET /api/v3/incidents.

betterstack_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. Uptime API: GET /api/v2/monitors.

betterstack_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.

betterstack_list_status_pages

List public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.

betterstack_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.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

acknowledge_incident

removed 22 Oct 2026

get_incident

removed 22 Oct 2026

get_monitor

removed 22 Oct 2026

list_heartbeats

removed 22 Oct 2026

list_incidents

removed 22 Oct 2026

list_monitors

removed 22 Oct 2026

list_on_call

removed 22 Oct 2026

list_status_pages

removed 22 Oct 2026

resolve_incident

removed 22 Oct 2026

Endpoints

URL	Transport	State	Latency	Checked
https://betterstack.usefulapi.io/mcp	streamable-http	answering	72 ms	11 min ago

Alternatives to Better Stack MCP by usefulapi

same job, measured the same way

StatusPage.me MCP by usefulapi

by usefulapi

Read status pages, incidents and monitors, and post incidents and maintenance in StatusPage.me.

14 tools answering

Spike.sh MCP by usefulapi

by usefulapi

Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.

16 tools answering

Squadcast MCP by usefulapi

by usefulapi

Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.

16 tools answering

Vantaj

by vantaj

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

13 tools answering

Statuspage MCP by usefulapi

by usefulapi

Read pages, components, incidents and maintenances; create and update incidents in Statuspage.

15 tools answering

StatusPal MCP by usefulapi

by usefulapi

Read status-page status, services, incidents and metrics; create, update and publish incidents.

11 tools answering

StatusCast MCP by usefulapi

by usefulapi

Read page status, components, uptime, incidents and content templates in StatusCast.

10 tools answering

StatOSS

by statoss

Status pages and uptime monitoring: read status, monitors and incidents; open incidents.

answering

Better Stack MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Better Stack MCP by usefulapi do?

It exposes 9 tools, read directly from the server on our last check. Among them: betterstack_acknowledge_incident, betterstack_get_incident, betterstack_get_monitor, betterstack_list_heartbeats, betterstack_list_incidents, betterstack_list_monitors and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Better Stack MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 157 ms. The bar chart above shows every period we have measured.

Did Better Stack MCP by usefulapi ever remove tools?

Yes. acknowledge_incident, get_incident, get_monitor, list_heartbeats and 5 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

How do I connect Better Stack MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Better Stack MCP by usefulapi need an API key?

No. Better Stack MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Better Stack MCP by usefulapi?

It answers our handshake in 157 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Better Stack MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at betterstack.usefulapi.io, which runs on its operator's own terms.