Stackpulse

app.stackpulse由 stackpulse.app 发布官方发布者v1.0.0更新于 Oct 24, 2026

8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.

已验证Streamable HTTP可网页运行效率与工作流安全与监控

概览

AI 生成的概览

让助手查询 9,700 多个服务的状态页，并管理 Stackpulse 仪表板与 URL 监控。

可以做什么
提供搜索 9,700 多个服务状态页、获取单个服务的状态、组件问题、90 天历史与近期事件，并列出当前出问题的服务。也可读取账号仪表板的整体状态、事件历史、URL 监控的可用率与证书信息，以及 7、30、90 天的可靠性分析。另可创建、重命名仪表板，增删服务，新增、立即检查、暂停与恢复 URL 监控。
适用场景
当你需要快速确认某个服务是否故障、查看自家仪表板与 URL 监控的实时状态，或想让助手协助创建与调整监控仪表板时使用。
运行要求
远程端点，无需本地运行环境。需有 Stackpulse 账号，且方案为 Pro。
安装前请注意
创建、重命名仪表板与增删服务、新增或暂停监控等操作会变更账号数据；暂停监控会结束进行中的事件并停止告警。新增 URL 监控时，请求头与请求体保留在应用内。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Stackpulse，将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

{
  "mcpServers": {
    "stackpulse": {
      "type": "http",
      "url": "https://stackpulse.app/mcp"
    }
  }
}

工具

16

search_services

Search services

Finds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.

输入参数query必填

get_service

Get a service

One service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.

输入参数slug必填

list_outages

List outages

Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.

输入参数alllimit

list_dashboards

List dashboards

The account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.

无需输入参数。

get_stack_status

Get stack status

What’s going on now on a dashboard: a summary, then every service and URL monitor with a problem, with when the problem began and when its current status did. A URL monitor that’s down lists what started around then. Without a dashboard, every dashboard.

输入参数includedashboard

get_incident_history

Get incident history

Incidents on a dashboard in a window: the ones that started in it (with what else started at the same time) and the ones already going on. As far back as the plan’s history goes.

输入参数todaysfromdashboard必填

get_monitor

Get a URL monitor

One of the account’s URL monitors: its status, its uptime over the last 30 days (or since it started) with the failed checks apart, response times, its certificate and its latest checks.

输入参数monitor必填

get_reliability

Get reliability

How reliable a dashboard’s services and URL monitors were over 7, 30 or 90 days: the least reliable first, with the share of time without a reported problem (minor issues count, so one long minor issue makes it low), time in each severity, incidents and recovery, and what tends to break together.

输入参数daysdashboard必填

create_dashboard

Create a dashboard

Makes a dashboard with a name and, optionally, services by slug (search_services finds them), within the plan’s dashboards and services. Answers with its address.

输入参数name必填services

rename_dashboard

Rename a dashboard

Renames a dashboard. Its status page shares the name.

输入参数name必填dashboard必填

add_services

Add services

Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.

输入参数services必填dashboard必填

remove_services

Remove services

Takes services off a dashboard. Their history stays; adding one back shows it again.

输入参数services必填dashboard必填

add_monitor

Add a URL monitor

Watches a website or API endpoint on a dashboard: checks the address once first, and refuses what the app refuses (private addresses, other ports, past the plan). Without a name, the page’s title names it. Headers and request bodies stay in the app.

输入参数url必填namedashboard必填

check_monitor

Check a URL monitor now

Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.

输入参数monitor必填

pause_monitor

Pause a URL monitor

Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.

输入参数monitor必填

resume_monitor

Resume a URL monitor

Resumes a paused URL monitor: it’s checked at once and starts fresh.

输入参数monitor必填

版本历史

1
  1. v1.0.0最新Oct 10, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库，或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用，因此这里不要求许可证。此检查项不计入百分比。