Stackpulse vs Statuspage
A side-by-side look at the Stackpulse and Statuspage MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
StackpulseMonitoring · Remote HTTP/SSE8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.51GoodAuth: not declaredVerdict: choose Stackpulse for monitoring work over a hosted endpoint; choose Statuspage for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Stackpulse when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_services, get_service, list_outages.
Choose Statuspage when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Stackpulse | |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 51/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 16 | Not listed |
| Full listing | View Stackpulse | View Statuspage |
Tools & capabilities
Stackpulse tools 16
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.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.list_outagesServices reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.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.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.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.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.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.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.rename_dashboardRenames a dashboard. Its status page shares the name.add_servicesAdds services to a dashboard by slug (search_services finds them), within the plan’s limit.remove_servicesTakes services off a dashboard. Their history stays; adding one back shows it again.- +4 more on the listing page
Statuspage tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Stackpulse
{
"mcpServers": {
"stackpulse": {
"url": "https://stackpulse.app/mcp"
}
}
}
Statuspage
{
"mcpServers": {
"statuspage": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-statuspage"
]
}
}
}
Frequently asked questions
Stackpulse is categorized under Monitoring and uses a remote HTTP/SSE transport. Statuspage belongs to Monitoring and uses a local stdio subprocess. Pick Stackpulse for monitoring work and Statuspage for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Stackpulse has no declared pricing — check the project's own site. Statuspage has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add stackpulse and statuspage as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Stackpulse has a quality signal of 51/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Statuspage has 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.