Stackpulse

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://stackpulse.app/mcp

claude mcp add --transport http stackpulse https://stackpulse.app/mcp

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

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

https://stackpulse.app/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月8日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

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

• get_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.

• list_outages

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

• 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

  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.

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

• get_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.

• 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 t

• create_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.

• rename_dashboard

  Renames a dashboard. Its status page shares the name.

• add_services

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

• remove_services

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

• add_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.

• check_monitor

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

• pause_monitor

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

• resume_monitor

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（stackpulse.app）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 194 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 16 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 18499 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 18499 个服务器的 62% 更新
• 基础检查结果等于或优于此分类中其他 18499 个服务器的 36%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README