Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 6
- 4 4
- 3 2
- 2 0
- 1 0
Trust in production
- Trust it - 83%
- With caveats - 0%
- Wouldn't - 17%
83% would recommend this server
How reviewers scored it
- Setup & docs 4.3
- Auth experience 4.3
- Reliability 4.1
- Maintainer responsiveness 4.4
Why it got an A
Hosted by incident.io at https://mcp.incident.io/mcp. Interactive users sign in with OAuth and actions are attributed to them (the connection lasts 28 days); automation can use an API key with scopes chosen when it is created, and a read-only access level never grants more. The docs list write tools that change real incidents: create, update, merge and message incidents, create and delete actions, page people through escalations, create schedule overrides and cover requests, and create maintenance windows. Status page updates are only drafted, and a person still publishes. The docs don't say whether the server asks before a write, so keep tool approval on in your client or use a read-only connection. Biggest deduction: the server itself is closed source, so this grade rests on incident.io's documentation and its MIT plugin repo (skills and config only, no server code) rather than code we could read, and we scored maintenance one band lower.
How to connect
Hosted: https://mcp.incident.io/mcp over HTTP; OAuth sign-in on first use. Claude Code: claude mcp add incident-io --transport http https://mcp.incident.io/mcpIs incident.io MCP Server safe?
Is incident.io MCP Server safe to use?
incident.io MCP Server grades A (strong public trust signals). Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested.
Does incident.io MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does incident.io MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Amplitude MCP ServerAmplitude's hosted MCP server for product analytics - search and query events, charts, dashboards, experiments, feature flags, cohorts and session replay, with OAuth sign-in and a separate EU endpoint.
- A Appwrite MCP ServerOfficial Appwrite server that exposes databases, users, functions, teams and storage as tools, hosted with OAuth or run locally with a project API key.
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Better Stack MCP ServerOfficial hosted Better Stack server to read and manage incidents, monitors, status pages and on-call, and run SQL over your logs, spans and metrics, with OAuth or an API token.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
Embed this badge
[](https://trustedmcp.io/servers/incident-io-mcp)<a href="https://trustedmcp.io/servers/incident-io-mcp"><img src="https://trustedmcp.io/badge/incident-io-mcp.svg" alt="TrustedMCP grade A" height="80"></a>Community reviews
Does what it says, no drama
Our agents call this dozens of times a day. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Good choice if you need incident.io in your agent.
Used for Automating release notes
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Easy win for our agent setup
Hooked incident.io MCP Server into Claude Code and it worked on the first try. Hosted endpoint means no local process to babysit. Scoped the token to just what the agent needs and it respected that. Happy to run it in production.
Used for Keeping project tickets in sync with code changes
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Good, but read the permissions first
I like it, with reservations. Filed an issue and got a reply within two days. I like that access goes through a proper sign-in instead of a long-lived secret on disk. For anything real I would look elsewhere.
Used for Internal developer assistant
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Saves me a context switch every hour
Tried it on a side project first, then rolled it out at work. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Easy recommendation.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Better than the DIY script it replaced
I use this almost daily. Scoped the token to just what the agent needs and it respected that. Being closed source, I cannot audit it, but the vendor has been responsive. Happy to run it in production.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Worth the five minutes to set up
Set this up for our team after comparing a few options. Sign-in flow was painless and I never had to paste a key into a config file. Would recommend without hesitation.
Used for Code review summaries for pull requests
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Our team uses it every day
Simple to set up in Cursor, simple to reason about. Auth is handled properly, and revoking access later was one click. Easy recommendation.
Used for Debugging sessions in Cursor
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Surprisingly polished
Replaced a homegrown script with incident.io MCP Server and have not looked back. Auth is handled properly, and revoking access later was one click. Good choice if you need incident.io in your agent.
Used for Letting a coding agent open and triage issues
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Recommended it to two teams already
Been running this for about a month now. Sign-in flow was painless and I never had to paste a key into a config file. It is in our production agent and I sleep fine.
Used for Looking up incident.io data without leaving the editor
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
The incident.io integration I wanted
Installed it on a Friday, it was part of my workflow by Monday. Sign-in flow was painless and I never had to paste a key into a config file. Would recommend without hesitation.
Used for CI failure investigation
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Handy for dev, careful in prod
Some tools are great, a couple feel half finished. I would prefer to read the code, but the hosted service has been dependable. Nothing to install, I just point the client at the URL. Scoped the token to just what the agent needs and it respected that.
Used for Scripting routine maintenance tasks
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Solid and well behaved
Of the incident.io integrations I tried, this one is the most predictable. Auth is handled properly, and revoking access later was one click. Being official from incident.io counts for a lot when I pitch it to security. It is in our production agent and I sleep fine.
Used for Generating boilerplate from existing patterns
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.