SERVER

incident.io

Rank #53640

pulsemcp/incident-io

Connects to incident.io for incident management, alert handling, on-call scheduling, and investigation workflows.

Not versioned
First listed
Mar 1, 2026
Last publish date
OVERVIEW

incident.io is a Model Context Protocol (MCP) server. It ranks #53640 of 58,900 servers tracked on MCP Toplist. incident.io is listed on PulseMCP, and ships as a single rolling release with no explicit version metadata. It was first listed on Mar 1, 2026.

STANDING
#53,640of 58,900 tracked servers

Ranks ahead of 5,260 of 58,900 servers on MCP Toplist.

CONNECT

Use incident.io

Add incident.io to any MCP client (Claude, Cursor, VS Code, …) with one of the configs below.

Remote · HTTP
{
  "mcpServers": {
    "incident-io": {
      "url": "https://mcp.incident.io/mcp"
    }
  }
}

This endpoint requires authentication — see the server’s docs for credentials.

REGISTRIES

Listed on 1 registry

VERSIONS

Not versioned

This server is published through a registry that does not expose explicit version metadata, and no GitHub release tags were found on the linked repository. The listing tracks a single rolling release.

FAQ

Frequently asked questions

What is incident.io?
Connects to incident.io for incident management, alert handling, on-call scheduling, and investigation workflows.
Is incident.io an official MCP server?
incident.io is not on the Official MCP Registry. It is listed on PulseMCP.
How many versions does incident.io have?
incident.io ships as a single rolling release with no explicit version metadata.
EXPLORE
incident.io - MCP Server #53640 | MCP Toplist