bots.st/stackpulse
Stackpulse
Website and API status monitoring
2970 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 16
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://stackpulse.app/mcp
What it can do
| Tool | What it says it does |
|---|---|
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. |
add_services | Adds services to a dashboard by slug (search_services finds them), within the plan’s limit. |
check_monitor | Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got. |
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. |
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. |
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. |
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. |
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. |
list_outages | Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given. |
pause_monitor | Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed. |
remove_services | Takes services off a dashboard. Their history stays; adding one back shows it again. |
rename_dashboard | Renames a dashboard. Its status page shares the name. |
resume_monitor | Resumes a paused URL monitor: it’s checked at once and starts fresh. |
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. |
In its maker's words
8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.
- Website
- stackpulse.app/mcp
- Publisher
- stackpulse.app
- Listed from
- the official MCP Registry as
app.stackpulse/mcp - Version
- 1.0.0, updated 10 Oct 2026
- Kinds of work
- Travel, maps and weather, Domains and websites, Other work
The domain it lives on
- stackpulse.app
- registered 9 Jan 2024 (2 years ago), at Name.com, Inc.
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2970 ms | |
| Answered | 2778 ms | |
| Answered | 1235 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.