Statuspage

What Statuspage MCP server does

The Statuspage MCP server retrieves operational data from vendors that publish the Atlassian Statuspage v2 JSON contract. It can report a vendor’s overall indicator, status description, degraded components, active incidents, recent incident updates, and scheduled maintenance. The data comes from each vendor’s own status host rather than from a separate monitoring database.

Coverage includes a curated map of 190 vendors spanning AI and model providers, cloud and hosting services, databases and observability products, developer tools, payments, communications, and business software. A request can also provide a specific status_host for a vendor outside that map. Responses identify whether the result came from the curated map or from the caller-supplied host.

How it works

The Statuspage MCP server reads the Statuspage v2 endpoints for status, summary, components, incidents, unresolved incidents, and maintenance information. It verifies the hosts in its curated map against the expected JSON endpoints instead of constructing hostnames without validation.

For a vendor check, the service returns structured result fields such as found, operational, open incidents, and the source used. “All Systems Operational” is treated as a successful operational result. If a page cannot be fetched, the response reports status_page_unreachable; an unknown vendor reports vendor_not_covered and may include near matches.

Some vendors publish status through other systems or formats. For those entries, the service identifies the vendor as unsupported for Statuspage data and provides a URL for a human to open. Certain Statuspage hosts omit the unresolved-incidents endpoint; the service filters the regular incident feed instead and reports the incident source it used.

Setup and configuration

You can connect to the hosted MCP endpoint at https://gateway.pipeworx.io/statuspage/mcp. The README names Claude Desktop, Cursor, and Windsurf as compatible client examples. The hosted connection also exposes shared Pipeworx gateway tools in addition to the pack’s own tools.

For a local connection, run the package as a stdio server with:

{
  "mcpServers": {
    "statuspage": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-statuspage"]
    }
  }
}

This local mode does not require a Pipeworx account and exposes only the Statuspage tools. The package can also be started directly with npx -y @pipeworx/mcp-statuspage. No API key or authentication is required by the data source, and the pack does not provide rate-limit handling.

Tools and capabilities

• statuspage_check checks one vendor or host and can include component details.
• statuspage_incidents returns incident history, with options for unresolved incidents, result limits, and all updates.
• statuspage_list_vendors searches the curated vendor map and can include vendors whose status information is published elsewhere.
• statuspage_multi_check checks up to 20 vendors, removes duplicate hosts, limits concurrency to five, and returns a compact table with a roll-up.

The Statuspage MCP server can also be called over HTTP through the gateway’s tool endpoint. Agents may use the gateway’s ask_pipeworx tool to ask questions in natural language, although that capability belongs to the gateway connection rather than the standalone local server.

Limitations and notes

The service only answers directly from Atlassian Statuspage v2-compatible feeds. Vendors using another status format are not silently substituted with a guessed source. The curated map is finite, so callers must provide a verified host for vendors outside it. A successful fetch with no incidents is distinct from a failed fetch, and clients should inspect the result fields rather than treating every empty incident list as proof that a page was reachable.

The integration is independent and unofficial. It is licensed under MIT.