Better Stack MCP by usefulapi
io.usefulapi/betterstackusefulapi.iostreamable-httpv1.41.4Scanned
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
9 tools: 2 change things and 7 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 1
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
2 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Better Stack MCP by usefulapi can do
The Better Stack MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 9 tools. It can create or change data (2 tools: betterstack_acknowledge_incident and betterstack_resolve_incident), but cannot delete data. 7 tools only read.
1 tool reads private data (betterstack_list_on_call); 2 tools bring in text other people can write (betterstack_list_monitors and betterstack_get_monitor); 1 tool can send data out of your system (betterstack_list_monitors). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Oct 25, 2026, version 1.41.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 2Claude Code: ask
betterstack_acknowledge_incidentAcknowledge an ongoing incident, signalling that someone is looking into it (stops further escalation).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Annotations the server declares
- title: Acknowledge an incident
- readOnlyHint: false
- idempotentHint: true
betterstack_resolve_incidentResolve an ongoing incident, marking it as handled/closed.1 finding
Why it is in this group
- The name "betterstack_resolve_incident" says "resolve": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "betterstack_resolve_incident" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"idempotentHint":true}; The name "betterstack_resolve_incident" says "resolve": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Resolve an incident
- readOnlyHint: false
- idempotentHint: true
Only reads 7Show 7 read-only tools
betterstack_get_incidentGet a single incident by id, including cause, status, timeline timestamps (started/acknowledged/resolved), who acknowledged/resolved it, and the related monitor.No findings
Why it is in this group
- The name "betterstack_get_incident" says "get": a word for reading.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get an incident
- readOnlyHint: true
betterstack_get_monitorGet a single monitor by id, including current status, last_checked_at, SSL/HTTP settings, regions, and alerting configuration.Reads text others writeNo findings
Why it is in this group
- The name "betterstack_get_monitor" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it 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}.
Annotations the server declares
- title: Get a monitor
- readOnlyHint: true
betterstack_list_heartbeatsList heartbeats (cron/background-job monitors that expect a periodic ping), with period, grace, and status (up/down/paused/pending).No findings
Why it is in this group
- The name "betterstack_list_heartbeats" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List heartbeats
- readOnlyHint: true
betterstack_list_incidentsList incidents (alerts triggered by monitors/heartbeats), filterable by date range, monitor, and acknowledged/resolved state.No findings
Why it is in this group
- The name "betterstack_list_incidents" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List incidents
- readOnlyHint: true
betterstack_list_monitorsList uptime monitors with their status (up/down/paused/pending/maintenance/validating), check frequency, and alert settings.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "betterstack_list_monitors" says "list": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
Annotations the server declares
- title: List monitors
- readOnlyHint: true
betterstack_list_on_callList on-call calendars/schedules and the users currently on call for escalation.Reads private dataNo findings
Why it is in this group
- The name "betterstack_list_on_call" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "calendar": it reads calendars.
Description, as the server wrote it 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.
Annotations the server declares
- title: List on-call schedules
- readOnlyHint: true
betterstack_list_status_pagesList public/private status pages with company name, subdomain, aggregate_state, and published flag.No findings
Why it is in this group
- The name "betterstack_list_status_pages" says "list": a word for reading.
Description, as the server wrote it List public/private status pages with company name, subdomain, aggregate_state, and published flag. Uptime API: GET /api/v2/status-pages.
Annotations the server declares
- title: List status pages
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__betterstack__betterstack_list_monitors"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://betterstack.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://betterstack.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
The server marks "betterstack_resolve_incident" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"idempotentHint":true}; The name "betterstack_resolve_incident" says "resolve": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://betterstack.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://betterstack.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Tools9 added, 9 removed.+9 added−9 removedView diff
- Added:betterstack_acknowledge_incidentChanges things
- Added:betterstack_get_incidentOnly reads
- Added:betterstack_get_monitorOnly reads
- Added:betterstack_list_heartbeatsOnly reads
- Added:betterstack_list_incidentsOnly reads
- Added:betterstack_list_monitorsOnly reads
- Added:betterstack_list_on_callOnly reads
- Added:betterstack_list_status_pagesOnly reads
- Added:betterstack_resolve_incidentChanges things
- Removed:acknowledge_incident
- Removed:get_incident
- Removed:get_monitor
- Removed:list_heartbeats
- Removed:list_incidents
- Removed:list_monitors
- Removed:list_on_call
- Removed:list_status_pages
- Removed:resolve_incident
Install
Pinned to version 1.41.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http betterstack https://betterstack.usefulapi.io/mcpclaude mcp add --transport http betterstack https://betterstack.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__betterstack__betterstack_get_monitor",
"mcp__betterstack__betterstack_list_incidents",
"mcp__betterstack__betterstack_get_incident",
"mcp__betterstack__betterstack_list_heartbeats",
"mcp__betterstack__betterstack_list_on_call",
"mcp__betterstack__betterstack_list_status_pages"
],
"ask": [
"mcp__betterstack__betterstack_list_monitors",
"mcp__betterstack__betterstack_acknowledge_incident",
"mcp__betterstack__betterstack_resolve_incident"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as betterstack. Review it before you use it.
Capability tags behind 3 rules
- mcp__betterstack__betterstack_list_monitors untrusted-input, outbound
- mcp__betterstack__betterstack_get_monitor untrusted-input
- mcp__betterstack__betterstack_list_on_call private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/betterstack/verify?hash=7db2d8470468cf5edbbec2ced837a3b7d286728c76dbfc5116ce21373dc3ef57" | jq -e '.changed == false'Pinned hash 7db2d8470468, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/betterstack/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/betterstack)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.
Better Stack MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Better Stack MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 9 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Better Stack MCP by usefulapi delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Better Stack MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Better Stack MCP by usefulapi have?
- 9 tools: 2 write, 7 read. betterstack_acknowledge_incident, betterstack_resolve_incident, betterstack_list_monitors, betterstack_get_monitor, betterstack_list_incidents, betterstack_get_incident, betterstack_list_heartbeats, betterstack_list_on_call and 1 more.
Does the Better Stack MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Better Stack MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): betterstack_list_monitors.
Has the Better Stack MCP by usefulapi changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.