All servers · Monitoring & logs

Stackpulse

app.stackpulse/mcp · v1.0.0

Measured by MCP Station

Description written by the publisher, not verified

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

Connect

claude mcp add --transport http mcp https://stackpulse.app/mcp

{
  "mcpServers": {
    "mcp": {
      "url": "https://stackpulse.app/mcp"
    }
  }
}

Tools as reported by the server

• 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 URL monitor that’s down lists what started around then. Without a dashboard, every dashboard.
• 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.
• 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.
• 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.
• 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.
• 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 write/delete
  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). 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.
• 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.

Website · JSON · Text for agents · Registry updated 2026-10-10