incident.io
Incident.io is an all-in-one AI platform for on-call, incident response, and status pages built for fast-moving teams.
Content
70% of score
—
2 of 15 buyer questions answered
Your site doesn't cover
- pricing
- technical
- limits
Fix list
12 to ship · 0 passing
Also covered by incident.io
Try it yourself
Sitedex already serves incident.io as an MCP endpoint. Ask it anything an AI agent might — see what comes back.
Snippets & configs
For developers and the engineer-on-call: copy these into your tools or your site.
MCP endpoint
https://mcp.sitedex.dev/s/incident-io/mcp
The URL anyone's agent points at. Read-only; safe to share.
Claude Code
claude mcp add incident --transport http https://mcp.sitedex.dev/s/incident-io/mcp
One command, then the agent has it.
Cursor / Continue
{
"mcpServers": {
"incident": {
"url": "https://mcp.sitedex.dev/s/incident-io/mcp"
}
}
}Drop into mcp.json.
WebMCP — two parts
WebMCP-capable browsers run the widget at runtime. Crawlers without JS rendering need the discovery manifest to find your tool surface. Install both.
1 · Widget script
<script async src="https://sitedex.dev/widget.js"></script>
Drop in <head>. WebMCP-capable browsers (Chrome 146+ Origin Trial) call navigator.modelContext.provideContext() via this script.
2 · Discovery manifest
{
"$schema": "https://wellknownmcp.org/schemas/webmcp.json",
"name": "incident.io",
"tools": [
{ "name": "search", "description": "Search incident.io's indexed content." },
{ "name": "get_page", "description": "Fetch a page from incident.io as markdown." }
]
}Host alongside the script at /.well-known/webmcp.json. Crawlers that don't render JS rely on this.
About this audit
Sitedex audits AI-readiness across 15 buyer questions and 11 protocol items. Each crawl produces a fresh report.
Question outcomes
- Answered cleanly2
- Partial4
- Unanswered9
Sitedex
incident.io is indexed by Sitedex. See more sites →