Stackpulse is answering right now. Last checked 7 min ago. It exposes 16 tools.
8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.
Uptime history
30 days of history
30 days agonow
100.0%
Uptime 24h
91 of 91 checks
16
Tools
read from the server
249 ms
Response time
average over 24h
open, no key
Access
streamable-http
Nothing serious here today
Today is the operative word: we check Stackpulse every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.
run in your terminal
claude mcp add mcp --transport http https://stackpulse.app/mcpSettings → Connectors → Add custom connector, then paste this address
https://stackpulse.app/mcp~/.codex/config.toml
[mcp_servers.mcp]
url = "https://stackpulse.app/mcp".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://stackpulse.app/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://stackpulse.app/mcp"
}
}
}Available tools 16
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
monitor
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.
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.
services
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.
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.
dashboard
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.
dashboards
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.
incident
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.
outages
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
pause_monitor
Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.
reliability
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.
rename
rename_dashboard
Renames a dashboard. Its status page shares the name.
resume
resume_monitor
Resumes a paused URL monitor: it’s checked at once and starts fresh.
service
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.
stack
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://stackpulse.app/mcp | streamable-http | answering | 221 ms | 7 min ago |
Alternatives to Stackpulse
same job, measured the same waylosclouds
by losclouds
Cloud and SaaS service status, plus your team's monitors, status pages, incidents, and alerts.
Statuser
by statuser-cloud
Monitor services, manage incidents and status pages in Statuser.cloud from your AI assistant.
Metricwatch
by cloudcorprecords
Datadog metrics, dashboards, logs, incidents, and monitors from your MCP client.
FlareWarden
by flarewarden
Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages.
openstatus
by openstatus
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
StackWitness
by stackwitness
Independent monitoring: status, monitors, and incidents from your StackWitness workspace.
Sentry
by mcparmory
Track errors, manage performance alerts, and configure dashboards and monitors
Dashmetrics
by cloudcorprecords
Grafana dashboards, datasources, Prometheus, Loki, and alerts from your MCP client.
Stackpulse — questions
Answers built from our own checks of this server.
What can Stackpulse do?
It exposes 16 tools, read directly from the server on our last check. Among them: add_monitor, add_services, check_monitor, create_dashboard, get_incident_history, get_monitor and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Stackpulse mostly used for?
Its tools cluster around monitor and services. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Stackpulse working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 249 ms. The bar chart above shows every period we have measured.
How do I connect Stackpulse?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Stackpulse need an API key?
No. Stackpulse completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Stackpulse?
It answers our handshake in 249 ms on average, which is faster than 55% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.