Stackpulse MCP server

Which servers in the official MCP registry are Stackpulse's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-18

← Back to Stackpulse

Whose server it is

Registry nameapp.stackpulse/mcpverified in the MCP registry

The registry name sits under stackpulse.app. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-18

Stateanswerschecked 2026-10-18
Tools16
Server calls itselfstackpulse
Server version1.0.0
Protocol version2025-06-18

On 2026-10-18 the server answered initialize and tools/list without a sign-in. First answer in 187 ms.

Tools it offers16 tools · read 2026-10-18

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.