Skip to content
MCP server

Stackpulse

By stackpulseAll Stackpulse servers

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

First seen 10 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

1
Directories
Collected by InvokeRank
16
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
-
GitHub stars
No repository data

Tools

ToolDescriptionBehaviour
add_monitorWatches 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.Changes data
add_servicesAdds services to a dashboard by slug (search_services finds them), within the plan’s limit.Changes data
check_monitorChecks one of the account’s URL monitors now, as Check now does in the app, and says what it got.Changes data
create_dashboardMakes 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.Changes data
get_incident_historyIncidents 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.Read-only
get_monitorOne 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.Read-only
get_reliabilityHow 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.Read-only
get_serviceOne service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.Read-only
get_stack_statusWhat’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.Read-only
list_dashboardsThe account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.Read-only
list_outagesServices reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.Read-only
pause_monitorPauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.Changes data
remove_servicesTakes services off a dashboard. Their history stays; adding one back shows it again.Destructive
rename_dashboardRenames a dashboard. Its status page shares the name.Changes data
resume_monitorResumes a paused URL monitor: it’s checked at once and starts fresh.Changes data
search_servicesFinds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.Read-only

Directory listings

DirectoryListingTierFirst seen
Official MCP RegistryStackpulse-10 Oct 2026