mcpbeat Sign in

Statuspage Incidents MCP Server

answering

Statuspage Incidents is answering right now. Last checked 3 min ago. It exposes 1 tools.

Read-only: recent incidents from public Atlassian Statuspage pages. Free, no API key.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
1071 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Statuspage Incidents every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add statuspage-incidents --transport http https://looper-products.fly.dev/mcp-statuspage/
Settings → Connectors → Add custom connector, then paste this address
https://looper-products.fly.dev/mcp-statuspage/
~/.codex/config.toml
[mcp_servers.statuspage-incidents]
url = "https://looper-products.fly.dev/mcp-statuspage/"
.cursor/mcp.json
{
  "mcpServers": {
    "statuspage-incidents": {
      "url": "https://looper-products.fly.dev/mcp-statuspage/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "statuspage-incidents": {
      "type": "http",
      "url": "https://looper-products.fly.dev/mcp-statuspage/"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

statuspage
get_statuspage_incidents
Read-only: fetch recent incidents from a public Atlassian Statuspage-hosted status page (e.g. https://www.githubstatus.com) via its free, unauthenticated JSON API at <base>/api/v2/incidents.json. Returns each incident's name, status, impact, created_at, resolved_at and shortlink. No login or API key.

Endpoints

URLTransportStateLatencyChecked
https://looper-products.fly.dev/mcp-statuspage/ streamable-http answering 294 ms 3 min ago

Alternatives to Statuspage Incidents

same job, measured the same way
Statuspage MCP
by mrfentmen

Query Statuspage management API: pages, page details, incidents.

288 installs/wk local only
Pingcheck MCP
by churman1113

PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.

45 installs/wk local only
StatusPal MCP by usefulapi
by usefulapi

Read status-page status, services, incidents and metrics; create, update and publish incidents.

11 tools answering
Vendor Status MCP
by approj

Status-page map for 1,100+ SaaS/cloud vendors plus 15,700+ incidents. No API key.

local only
Openuptime
by openuptime

Manage uptime monitors, incidents and status pages from any MCP client.

answering
StatusPage.me MCP by usefulapi
by usefulapi

Read status pages, incidents and monitors, and post incidents and maintenance in StatusPage.me.

14 tools answering
StatOSS
by statoss

Status pages and uptime monitoring: read status, monitors and incidents; open incidents.

answering
Uptimepage
by uptimepage

Monitor uptime and incidents, run checks, and publish status updates from your Uptimepage org.

41 tools answering

Statuspage Incidents — questions

Answers built from our own checks of this server.

What can Statuspage Incidents do?
It exposes 1 tools, read directly from the server on our last check. Among them: get_statuspage_incidents. 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 →
Is Statuspage Incidents 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 1071 ms. The bar chart above shows every period we have measured.
How do I connect Statuspage Incidents?
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 Statuspage Incidents need an API key?
No. Statuspage Incidents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Statuspage Incidents?
It answers our handshake in 1071 ms on average, which is faster than 5% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.