Incident Postmortem Prover MCP Connector for Claude
A+Most postmortems fail: vague timelines, symptom-level root causes, and action items with no owner. This tool forces SRE-grade rigor: minute-by-minute timeline reconstruction, systemic 5-Whys analysis, root cause isolation, accountable action items with owners and deadlines, and historical pattern detection.
70% of incident postmortems fail at root cause identification. Teams write 'add monitoring' as an action item and move on. The same incident recurs 3 months later.
The 5 Postmortem Failures This Tool Prevents
- TIMELINE_INCOMPLETE — No minute-by-minute reconstruction. 'Around 3 PM something happened' is not a timeline.
- ROOT_CAUSE_SHALLOW — Stopped at the symptom. 'The server crashed' is what happened, not WHY it happened.
- CAUSES_CONFLATED — Root cause mixed with contributing factors. The trigger is not the vulnerability.
- ACTIONS_UNACCOUNTABLE — 'Add monitoring' has no owner, no deadline, no success metric.
- PATTERN_IGNORED — No comparison with previous incidents. This may be the 3rd time this quarter.
The engine enforces 5 Decision Pivots with semantic trap lists that catch vague timelines, shallow analysis, conflated causes, hand-wavy actions, and dismissed patterns.
Related Connectors
Elon Musk Physics Prover MCP
An AI accepted every constraint as given, added layers of complexity, and automated bloated processes. That is consulting, not engineering. This tool forces the 5-Step Starbase Algorithm: question requirements, delete parts, simplify survivors, accelerate cycle time, automate last.
Data Analysis Prover MCP
A marketing team asked an AI to analyze campaign data. The AI reported 'significant correlation between email frequency and purchase rate (p<0.05).' The team tripled emails. Unsubscribes spiked 340%. Sample: N=47 self-selected respondents, no power analysis. Correlation: observational, no confounders. Distribution: right-skewed but mean used. p=0.043 but Cohen's d=0.12 — trivial. Chart: truncated Y-axis making a 2% difference look enormous. This tool forces five axes: sample validity, causal inference, distribution awareness, significance with effect size, and visualization integrity.
Engineering Reasoning Prover MCP
An engineering report cited 'industry standards' without naming a single one. Engineering Reasoning Prover forces ISO/ASME/IEC-grounded compliance analysis — real calculations, real codes, real risk quantification.
Weather Damage Claim Plan MCP
Generate structured notification workflows and safety-first mitigation task plans for weather-related property damage.