mcpbeat Sign in

Incident Io MCP Server

by incident-io Your server? Claim it
answering

Incident Io is answering right now. Last checked 14 min ago.

Uptime history 51 days of history · worst day 99%
51 days agonow
100.0%
Uptime 24h
90 of 90 checks
—
Tools
hidden behind auth
95 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Incident Io 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 14 min ago.

run in your terminal
claude mcp add mcp --transport http https://mcp.incident.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.incident.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.incident.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.incident.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.incident.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mcp.incident.io/mcp streamable-http sign-in 82 ms 14 min ago

Alternatives to Incident Io

same job, measured the same way
Ai Incident Db
by pipeworx-io

AI Incident Database (AIID) MCP

35 tools answering
AlertOps
by wyre-ai

MCP server for AlertOps' incident alerting/on-call API.

local only
Instatus
by usefulapi

Manage status pages: components, incidents and maintenances; set live component status.

14 tools answering
Journald MCP Server
by james116blue

Incident forensic with log files analyzing

50 installs/wk local only
Rootly
by mcparmory

Manage incident alerts, events, and workflows with custom automations

292 installs/wk local only
mttrly
by mttrly

AI-powered incident management and server monitoring via MCP.

answering
Rootly
by wyre-ai

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

local only
Rootly
by wyre-technology

MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.

local only

Incident Io — questions

Answers built from our own checks of this server.

Why is there no tool list for Incident Io?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Incident Io working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 90 checks got a reply (100.0%), average response time 95 ms. The bar chart above shows every period we have measured.
How do I connect Incident Io?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Incident Io?
No API key is involved. Incident Io answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Incident Io?
It answers our handshake in 95 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.