Is the Incident-Investigator MCP server actively maintained?

The Incident-Investigator MCP server was last committed 1mo ago and has 0 contributors. Issue health: 50% of issues resolved. AgentRank freshness score reflects real-time maintenance activity.

Incident-Investigator MCP Server

Name: stackrail-io/Incident-Investigator
Rating: 2.6 (1 reviews)
Author: stackrail-io

stackrail-io/Incident-Investigator

Score: 41.1 Rank #13249 MCP Server

Are you the maintainer of stackrail-io/Incident-Investigator? Claim this listing →

Stateful MCP server for incident investigation: dynamic evidence planning, competing hypotheses, confidence scoring, timelines, blast radius, and postmortems. Works with Cursor, Claude Code, Codex, and any MCP client.

Add AgentRank to Claude Code Discover and compare tools like stackrail-io/Incident-Investigator — your AI finds the right one automatically

Get API Access →

claude mcp add agentrank -- npx -y agentrank-mcp-server

Overview

stackrail-io/Incident-Investigator is a Go MCP server licensed under MIT. Stateful MCP server for incident investigation: dynamic evidence planning, competing hypotheses, confidence scoring, timelines, blast radius, and postmortems. Works with Cursor, Claude Code, Codex, and any MCP client.

Ranked #13249 out of 24850 indexed tools.

Ecosystem

Go MIT

Score Breakdown

Stars 15% 1

1 stars → early stage

Freshness 25% 1mo ago

Last commit 1mo ago → moderate activity

Issue Health 25% 50%

No issues filed → no history to score

Contributors 10% 0

0 contributors → solo project

Dependents 25% 0

No dependents → no downstream usage

npm Downloads N/A

PyPI Downloads N/A

Forks 1

Description Detailed

License MIT

Weights: Freshness 20% · Issue Health 20% · Dependents 22% · Stars 10% · Contributors 8% · How we score →

How to Improve

Freshness high impact

Last commit was 45 days ago — a recent commit would boost your freshness score

Contributors medium impact

Single-contributor projects carry bus-factor risk — welcoming contributors boosts confidence

Dependents medium impact

No downstream dependents detected yet — adoption by other projects is the strongest trust signal

Badge all embed codes →

Markdown

[![AgentRank](https://agentrank-ai.com/api/badge/tool/stackrail-io--Incident-Investigator)](https://agentrank-ai.com/tool/stackrail-io--Incident-Investigator/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge)

HTML

<a href="https://agentrank-ai.com/tool/stackrail-io--Incident-Investigator/?utm_source=badge&utm_medium=readme&utm_campaign=agentrank_badge"><img src="https://agentrank-ai.com/api/badge/tool/stackrail-io--Incident-Investigator" alt="AgentRank"></a>

Embed Widget docs →

HTML

<script src="https://agentrank-ai.com/embed.js" data-tool="stackrail-io/Incident-Investigator"></script>

Details

Stars: 1
Forks: 1
Open Issues: 0
Closed Issues: 0
Contributors: 0
Dependents: —
Language: Go
License: MIT
Last Commit: 1mo ago

Matched Queries

"mcp server""mcp-server"

See alternatives to stackrail-io/Incident-Investigator → Browse mcp-server category → Compare stackrail-io/Incident-Investigator → How to Build an MCP Server in 2026 →MCP Server Comparison: Top 10 Head-to-Head →

View on GitHub →