Better Stack MCP by usefulapi

io.usefulapi由 usefulapi.io 发布官方发布者v1.37.5更新于 Nov 8, 2026

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

发布方自己的服务：Ably MCP by usefulapi

已验证Streamable HTTP可网页运行云端与基础设施安全与监控

服务详情

标识符: io.usefulapi/betterstack
传输: Streamable HTTP
运行时: Web executable
信任: Verified
发布于: Sep 16, 2026

安全提示

MCP 服务会接收对话中的工具调用请求，并可能执行外部操作。启用前请先了解该服务能做什么，并只授予它所需的权限。

注册中心已验证此服务的命名空间属于 usefulapi.io，且该域名同时运行其端点。这可以确认发布者，但并不代表该服务的工具是安全的。

SourceWeft 的检查只涵盖条目是否完整、端点是否响应；不审查服务器的代码，也不审查其工具的行为。

在 README 中添加徽章

向读者展示该 MCP 服务已收录于 SourceWeft，徽章链接到本页。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.usefulapi%2Fbetterstack.svg)](https://sourceweft.com/mcp/io.usefulapi%2Fbetterstack?utm_source=readme&utm_medium=badge)

概览

AI 生成的概览

面向 Better Stack Uptime 的托管 MCP 服务器：让助手读取监控项、事件、心跳、值班表和状态页，并可确认或解决事件。

可以做什么: 列出并查看监控项的状态、检查频率、区域和告警设置
列出并查看事件的原因、时间线时间戳以及确认或解决人
列出定时任务/后台任务的心跳及其周期、宽限时间和状态
列出值班表与当前值班人员，以及状态页及其汇总状态
确认或解决进行中的事件
查看本月工具调用用量、提交功能请求或管理 Pro 订阅
适用场景: 适合想通过对话了解当前故障、近期事件历史或谁在值班，并直接在聊天中确认或解决事件，而不必打开 Better Stack 控制台的场景。
运行要求: 通过 streamable HTTP 连接的远程端点，无需本地安装。使用 OAuth 登录，首次连接时需粘贴 Better Stack API 令牌（Better Stack → Settings → API tokens），按用户存储。客户端配置中不要填写 API 密钥或 Authorization 头。超出免费月度调用额度后需要付费方案。

安装前请注意

OAuth 登录过程中会要求提供 Better Stack API 令牌，并由第三方托管方存储。确认和解决工具会改变事件状态并停止或关闭升级通知，执行前应确认。用量按调用计费：免费方案每月 50 次工具调用；升级工具会返回 Pro（每月 9 美元）或 Pro+（每月 39 美元）的 Stripe 结账链接；取消后服务持续到已付费周期结束，当期不退款。

安装

在 SourceWeft 中

打开控制台中的 Better Stack MCP by usefulapi，将其添加到工作区。
为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.usefulapi%2Fbetterstack/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "better-stack-by-usefulapi": {
      "type": "http",
      "url": "https://betterstack.usefulapi.io/mcp"
    }
  }
}

README

Better Stack MCP by usefulapi

Manage Better Stack Uptime from Claude, Cursor, or any MCP client — read monitors, incidents, heartbeats, on-call schedules and status pages, and acknowledge/resolve incidents. Hosted, no local install: connect with your Better Stack API token.

Live endpoint: https://betterstack.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://betterstack.usefulapi.io/mcp.
Claude Code: claude mcp add --transport http betterstack https://betterstack.usefulapi.io/mcp, then run /mcp to log in.
VS Code: Add to VS Code.
Cursor and other clients: add the URL as a remote MCP server:

json

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

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

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Better Stack credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/betterstack/

On first connect you'll paste your Better Stack API token (Better Stack → Settings → API tokens). It's validated, stored per-user, and scoped to you — no keys in config files.

Tools

Tool	Type	What it does
`betterstack_list_monitors`	read	List monitors
`betterstack_get_monitor`	read	Get a monitor
`betterstack_list_incidents`	read	List incidents
`betterstack_get_incident`	read	Get an incident
`betterstack_list_heartbeats`	read	List heartbeats
`betterstack_list_on_call`	read	List on-call schedules
`betterstack_list_status_pages`	read	List status pages
`betterstack_acknowledge_incident`	write	Acknowledge an incident
`betterstack_resolve_incident`	write	Resolve an incident
`betterstack_usage_status`	meta	Usage status (free-tier meter)
`betterstack_request_feature`	meta	Request a missing feature
`betterstack_upgrade`	meta	Upgrade to Pro or Pro+
`betterstack_cancel_subscription`	meta	Cancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with betterstack_upgrade (it returns a Stripe Checkout link). Cancel any time with betterstack_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running betterstack_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

来源：servers/betterstack/README.md，提交 4046075

工具

betterstack_list_monitors

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.

输入参数urlpageper_pageteam_namepronounceable_name

betterstack_get_monitor

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

输入参数monitor_id必填

betterstack_list_incidents

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.

输入参数tofrompageper_pageresolvedteam_namemonitor_idacknowledgedheartbeat_id

betterstack_get_incident

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

输入参数incident_id必填

betterstack_list_heartbeats

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.

输入参数pageper_pageteam_name

betterstack_list_on_call

List on-call schedules

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.

输入参数pageper_pageteam_name

betterstack_list_status_pages

List status pages

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

输入参数pageper_pageteam_name

betterstack_acknowledge_incident

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

输入参数incident_id必填acknowledged_by必填

betterstack_resolve_incident

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

输入参数incident_id必填resolved_by必填