Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Data access / search
8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Stackpulse
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http stackpulse https://stackpulse.app/mcpCapabilities
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.
DiscoveredAdds services to a dashboard by slug (search_services finds them), within the plan’s limit.
DiscoveredChecks one of the account’s URL monitors now, as Check now does in the app, and says what it got.
DiscoveredMakes 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.
DiscoveredIncidents 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.
DiscoveredOne 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.
DiscoveredHow 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.
DiscoveredOne service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.
DiscoveredWhat’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.
DiscoveredThe account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.
DiscoveredServices reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.
DiscoveredPauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.
DiscoveredTakes services off a dashboard. Their history stays; adding one back shows it again.
DiscoveredRenames a dashboard. Its status page shares the name.
DiscoveredResumes a paused URL monitor: it’s checked at once and starts fresh.
DiscoveredFinds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 465 ms | 16 |