Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/betterstack

REMOTE · BETTERSTACK.USEFULAPI.IO · SCANNED SEP 20

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

Available components

remote · betterstack.usefulapi.io 86
0 this week 86 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security78
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 940 tokens (~104/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.usefulapi/betterstack MCP server?

io.usefulapi/betterstack is a hosted endpoint at https://betterstack.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · betterstack.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-betterstack 'https://betterstack.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-betterstack": {
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-betterstack": {
      "type": "http",
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-betterstack]
url = "https://betterstack.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-betterstack": {
      "type": "remote",
      "url": "https://betterstack.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-betterstack --url 'https://betterstack.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-betterstack:
    url: "https://betterstack.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-betterstack": {
      "Transport": "http",
      "Url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-betterstack -t streamable-http -u 'https://betterstack.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-betterstack": {
      "type": "http",
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Sept 26 +2
    • Authorization: fail → pass ▲ security
  • 3 Sept 26 −2
    • Authorization: pass → fail ▼ security
  • 27 Aug 26 +2
    • Authorization: fail → pass ▲ security
  • 26 Aug 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +54
    • Authorization: unverified → pass ▲ security
    • Schema quality: unverified → fail ▼ functional
    • Schema quality: unverified → excellent ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → pass ▲ functional
    • Stability: fail → 0.97 functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 24 Aug 26 −54
    • Authorization: pass → unverified ▼ security
    • Stability: 0.90 → fail ▼ security
    • Schema quality: excellent → unverified ▼ functional
    • Schema quality: fail → unverified ▼ functional
    • Schema quality: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 23 Aug 26 +54
    • Authorization: unverified → pass ▲ security
    • Schema quality: unverified → fail ▼ functional
    • Schema quality: unverified → excellent ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Schema quality: unverified → pass ▲ functional
    • Stability: fail → 0.90 functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 22 Aug 26 31
    • Authorization: pass → unverified ▼ security
    • Stability: 0.83 → fail ▼ security
    • Schema quality: excellent → unverified ▼ functional
    • Schema quality: fail → unverified ▼ functional
    • Schema quality: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://betterstack.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 bee23a482f74ddfb1356e41a07fd2054
SANs: usefulapi.io, betterstack.usefulapi.io, *.betterstack.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of betterstack.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://betterstack.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" 

Bearer realm="OAuth", resource_metadata="https://betterstack.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document https://betterstack.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://betterstack.usefulapi.io/mcp
Authorisation server https://betterstack.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://betterstack.usefulapi.io/mcp Verified 200
http (plaintext) http://betterstack.usefulapi.io/mcp Inconclusive 401
MCP tools · 9 exposed · ~940 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
acknowledge_incident ~104

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.

NameTypeReqDescription
acknowledged_bystringyesUser e-mail or a custom identifier of who is acknowledging the incident.
incident_idstringyesThe incident id to acknowledge (from list_incidents).

No output schema declared.

No examples provided.

get_incident ~73

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

NameTypeReqDescription
incident_idstringyesThe incident id (from list_incidents).

No output schema declared.

No examples provided.

get_monitor ~66

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

NameTypeReqDescription
monitor_idstringyesThe monitor id (from list_monitors).

No output schema declared.

No examples provided.

list_heartbeats ~98

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.

NameTypeReqDescription
pageinteger–Page number for pagination (default 1).
per_pageinteger–Results per page.
team_namestring–Filter by team name (only when using a global API token).

No output schema declared.

No examples provided.

list_incidents ~197

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.

NameTypeReqDescription
acknowledgedboolean–true = only acknowledged, false = only unacknowledged.
fromstring–Start date yyyy-mm-dd (inclusive).
heartbeat_idstring–Only incidents for this heartbeat id.
monitor_idstring–Only incidents for this monitor id.
pageinteger–Page number for pagination (default 1).
per_pageinteger–Results per page.
resolvedboolean–true = only resolved, false = only unresolved.
team_namestring–Filter by team name (only when using a global API token).
tostring–End date yyyy-mm-dd (inclusive).

No output schema declared.

No examples provided.

list_monitors ~133

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.

NameTypeReqDescription
pageinteger–Page number for pagination (default 1).
per_pageinteger–Results per page.
pronounceable_namestring–Filter monitors by their pronounceable name.
team_namestring–Filter by team name (only when using a global API token).
urlstring–Filter monitors by their monitored URL.

No output schema declared.

No examples provided.

list_on_call ~91

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.

NameTypeReqDescription
pageinteger–Page number for pagination (default 1).
per_pageinteger–Results per page.
team_namestring–Filter by team name (only when using a global API token).

No output schema declared.

No examples provided.

list_status_pages ~86

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

NameTypeReqDescription
pageinteger–Page number for pagination (default 1).
per_pageinteger–Results per page.
team_namestring–Filter by team name (only when using a global API token).

No output schema declared.

No examples provided.

resolve_incident ~92

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.

NameTypeReqDescription
incident_idstringyesThe incident id to resolve (from list_incidents).
resolved_bystringyesUser e-mail or a custom identifier of who is resolving the incident.

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/betterstack MCP server?

io.usefulapi/betterstack is an MCP server listed in the public MCP registry as io.usefulapi/betterstack. Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents. This page covers its hosted endpoint (https://betterstack.usefulapi.io/mcp).

Is the io.usefulapi/betterstack MCP server safe to use?

io.usefulapi/betterstack scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.usefulapi/betterstack MCP server expose?

io.usefulapi/betterstack exposes 9 tools: list_monitors, get_monitor, list_incidents, get_incident, list_heartbeats, and 4 more. Their descriptions and schemas cost roughly 940 tokens of context every time the server is loaded.

Does the io.usefulapi/betterstack MCP server require authentication?

Yes. io.usefulapi/betterstack asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.usefulapi/betterstack MCP server still maintained?

io.usefulapi/betterstack is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.