An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Incident Postmortem Prover to ChatGPT and Claude

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Turn shallow incident narratives into rigorous technical investigations.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 1 capability

We ship only the actions that matter.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through Incident Postmortem Prover.

  1. 01

    Validate incident postmortem

    This capability audits your postmortem against five strict criteria: timeline completeness, depth of 5-Whys, separation of root causes from amplifiers, ODAS-compliant action items, and historical pattern matching.

Real work

What teams actually run

01

Post-Outage Auditing

Run your completed incident report through the MCP to see if it meets SRE standards.

02

Preventing Recurrence

Use the pattern detection to see if a current issue is a repeat of a previous quarter's failure.

03

Action Item Validation

Ensure every task assigned after a crisis has a clear owner and a way to measure success.

04

Training Junior Engineers

Use the capability's feedback to teach new hires how to conduct professional investigations.

Automate a task

Put Incident Postmortem Prover to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Incident Postmortem Prover works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Incident Postmortem Prover to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

872ms average. Fast in production.

Incident Postmortem Prover is checked daily against the live service.

Daily averagePeak 1352ms
Oct 3Today
Fastest day
623ms
Slowest day
1352ms
14-day trend
Improving-29%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 1 capability arrives ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Incident Postmortem Prover, so you can see the experience inside your AI.

It does not authenticate your account with Incident Postmortem Prover. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Incident Postmortem Prover Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_KJycaUpjREM4styaMUmvRCfmlrKrfVMXPwF6uM9b/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Incident Postmortem Prover capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "incident-postmortem-prover-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_KJycaUpjREM4styaMUmvRCfmlrKrfVMXPwF6uM9b/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Incident Postmortem Prover in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Incident Postmortem Prover owners hand off.

Site Reliability Engineers and DevOps teams who need to move past finger-pointing and toward systemic reliability.

  • 01

    SRE

    Uses the MCP to audit incident reports for technical rigor.

  • 02

    DevOps Engineer

    Hands off incident timelines to the agent to find process gaps.

  • 03

    Engineering Manager

    Uses the capability to ensure action items are actually assigned and measurable.

FAQ

Questions Incident Postmortem Prover owners ask.

  • 01

    What is an ODAS action item?

    ODAS stands for Owner, Deadline, Action, and Success metric. The MCP rejects any action item that does not include all four components.

  • 02

    How does this MCP help with root cause analysis?

    It uses a 5-Whys framework to push your agent beyond symptoms like 'the server crashed' toward systemic issues like 'insufficient automated testing'.

  • 03

    Can I use this with Claude or Cursor?

    Yes, you can connect this MCP to any compatible client including Claude, Cursor, and Windsurf.

  • 04

    What does a TIMELINE_INCOMPLETE verdict mean?

    It means your timeline has gaps. A proper investigation requires a minute-by-minute account of alerts, decisions, and actions in UTC.

  • 05

    Does this MCP host my data?

    Vinkius hosts the MCP and manages the connection, but you provide the incident data to your AI client for analysis.

  • 06

    What makes a timeline 'complete'?

    Minute-by-minute entries from first alert to full resolution. Each entry: [HH:MM] [Actor] [Action] [Outcome]. 'Around 3 PM' is rejected. '15:03. PagerDuty alert fired for p95 > 2s on /api/orders' is accepted.

  • 07

    How deep should the 5 Whys analysis go?

    Until you reach a SYSTEMIC root. not a human error. 'Bob forgot to restart' is blame. 'The deployment pipeline has no post-deploy health check' is a system fix. The 5th Why should expose a process, architecture, or policy gap.

  • 08

    What makes an action item 'accountable'?

    Three requirements: (1) Named owner. not 'the team'. (2) Deadline. not 'soon'. (3) Success metric. not 'improved'. Example: 'Owner: @maria, Deadline: 2024-02-15, Metric: p95 latency < 500ms for 7 consecutive days.'

Explore

More in Productivity

Suggestions

Connect Incident Postmortem Prover to Claude, Cursor, ChatGPT & more