# Stackpulse

- Registry name: `app.stackpulse/mcp` · version 1.0.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=app.stackpulse%2Fmcp
- Server page: https://mcpstation.net/s/app.stackpulse--mcp.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://stackpulse.app/mcp`

## Tools (as reported by the server, not verified)

- `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 to break together.
- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html