Stackpulse

Name: Stackpulse
Author: app.stackpulse

MCP serverMCP

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

by app.stackpulsehomepage ↗v1.0.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"stackpulse","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability41/41 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	116 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
10 h ago	mcp initialize	ok	200	177 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
16 h ago	mcp initialize	ok	200	109 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
22 h ago	mcp initialize	ok	200	86 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
29 h ago	mcp initialize	ok	200	273 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	131 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	85 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	96 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
3 d ago	mcp initialize	ok	200	103 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools
3 d ago	mcp initialize	ok	200	85 ms	server stackpulse 1.0.0 · protocol 2025-06-18 · 16 tools

Tools observed via MCP handshake

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.
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.
list_outages — Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.
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.
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
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 pl
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 certific
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 (mi
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 addres
rename_dashboard — Renames a dashboard. Its status page shares the name.
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.
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
check_monitor — Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.
pause_monitor — Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.
resume_monitor — Resumes a paused URL monitor: it’s checked at once and starts fresh.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryapp.stackpulse/mcp

first seen 11 d ago · fetched 2 d agoopen ↗

Field history (6 recent events)

11 d ago · declared · summary → "8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro."
11 d ago · declared · description → "8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro."
11 d ago · declared · publisherName → "app.stackpulse"
11 d ago · declared · homepageUrl → "https://stackpulse.app/mcp"
11 d ago · declared · version → "1.0.0"
11 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from