io.usefulapi/betterstack

REMOTE · BETTERSTACK.USEFULAPI.IO · SCANNED AUG 3

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

Available components

+4 this week 74 74 Trust /100

Trust breakdown (6 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 →

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 not yet verified: we couldn't determine whether a plaintext access path exists. 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

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability80

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 Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · betterstack.usefulapi.io

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http io-usefulapi-betterstack 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"

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

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 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
28 Jul 26 +1
- Stability: unverified → 0.03 ▲ functional
27 Jul 26 +58
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 12

First indexed and scored.

Show 6 earlier entries Hide earlier entries

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 3 Aug 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	16 Jul 2026	14 Oct 2026	ECDSA 256	ECDSA-SHA256	e615b24350208dba0e11518597d6a4f3
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

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

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.

Tool Tokens

acknowledge_incident Acknowledge an 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.

Input Output Examples

Name	Type	Req	Description
acknowledged_by	string	yes	User e-mail or a custom identifier of who is acknowledging the incident.
incident_id	string	yes	The incident id to acknowledge (from list_incidents).

No output schema declared.

No examples provided.

get_incident Get an 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}.

Input Output Examples

Name	Type	Req	Description
incident_id	string	yes	The incident id (from list_incidents).

No output schema declared.

No examples provided.

get_monitor Get a 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}.

Input Output Examples

Name	Type	Req	Description
monitor_id	string	yes	The monitor id (from list_monitors).

No output schema declared.

No examples provided.

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

Input Output Examples

Name	Type	Req	Description
page	integer	—	Page number for pagination (default 1).
per_page	integer	—	Results per page.
team_name	string	—	Filter by team name (only when using a global API token).

No output schema declared.

No examples provided.

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

Input Output Examples

Name	Type	Req	Description
acknowledged	boolean	—	true = only acknowledged, false = only unacknowledged.
from	string	—	Start date yyyy-mm-dd (inclusive).
heartbeat_id	string	—	Only incidents for this heartbeat id.
monitor_id	string	—	Only incidents for this monitor id.
page	integer	—	Page number for pagination (default 1).
per_page	integer	—	Results per page.
resolved	boolean	—	true = only resolved, false = only unresolved.
team_name	string	—	Filter by team name (only when using a global API token).
to	string	—	End date yyyy-mm-dd (inclusive).

No output schema declared.

No examples provided.

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

Input Output Examples

Name	Type	Req	Description
page	integer	—	Page number for pagination (default 1).
per_page	integer	—	Results per page.
pronounceable_name	string	—	Filter monitors by their pronounceable name.
team_name	string	—	Filter by team name (only when using a global API token).
url	string	—	Filter monitors by their monitored URL.

No output schema declared.

No examples provided.

list_on_call List on-call schedules ~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.

Input Output Examples

Name	Type	Req	Description
page	integer	—	Page number for pagination (default 1).
per_page	integer	—	Results per page.
team_name	string	—	Filter by team name (only when using a global API token).

No output schema declared.

No examples provided.

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

Input Output Examples

Name	Type	Req	Description
page	integer	—	Page number for pagination (default 1).
per_page	integer	—	Results per page.
team_name	string	—	Filter by team name (only when using a global API token).

No output schema declared.

No examples provided.

resolve_incident Resolve an 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.

Input Output Examples

Name	Type	Req	Description
incident_id	string	yes	The incident id to resolve (from list_incidents).
resolved_by	string	yes	User e-mail or a custom identifier of who is resolving the incident.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	12
27 Jul	70
28 Jul	71
29 Jul	71
30 Jul	70
31 Jul	72
1 Aug	73
2 Aug	73
3 Aug	74