Accident Investigation Prover Connector for AI agents.
1 live capability
Enforce ICAO Annex 13 standards and NTSB rigor in your aviation safety reports.
Waiting for input…
Why people use Accident Investigation Prover
Stop Shallow Blame with Accident Investigation Prover Aviation Safety Rigor
This Connector puts the investigation on a professional track. It rejects narrative-based guesses and forces the agent to correlate hard data points. You get a report that follows the HFACS taxonomy and identifies the actual organizational pressures, like budget cuts or audit gaps.
What Vinkius changes
Your agent stops guessing and starts performing a professional-grade aviation safety audit.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 5,900+ Connectors
- Real-world use case 01
Engine Failure Analysis
Investigating a turbine disk separation to find out if it was a maintenance gap or a supplier cost-cutting issue using validate_accident_investigation.
- Real-world use case 02
Terrain Impact Review
Analyzing a CFIT incident to see if visual illusions were compounded by inadequate crew pairing or training gaps.
- Real-world use case 03
Training Audit
Evaluating why a pilot lacked specific skills by tracing back to budget cuts and syllabus coverage gaps.
Complete set · 1capability
The complete Accident Investigation Prover capability set.
These are the exact actions your AI can choose when you ask it to work with Accident Investigation Prover.
01
1 capability in this set.
Part of 1 available through Accident Investigation Prover.
- 01 Capability
Validate accident investigation
Correlates evidence chains and classifies factors into the HFACS taxonomy. It forces the agent to identify organizational root causes and write measurable recommendations.
Set up in minutes
One URL. Then ask Accident Investigation Prover to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Accident Investigation Prover from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_lW5eq02uyQWDJiNGsxX901icN7Fl8AQ8SwMOpToG/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Accident Investigation Prover, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Accident Investigation Prover for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_lW5eq02uyQWDJiNGsxX901icN7Fl8AQ8SwMOpToG/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Accident Investigation Prover URL.
- Step 03
Save and start
Save the connection and enable Accident Investigation Prover in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"accident-investigation-prover": {
"url": "https://edge.vinkius.com/vk_preview_lW5eq02uyQWDJiNGsxX901icN7Fl8AQ8SwMOpToG/mcp"
}
}
} - Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Accident Investigation Prover
Open Agent mode in chat and ask: "Using Accident Investigation Prover, help me...". 1 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"accident-investigation-prover": {
"url": "https://edge.vinkius.com/vk_preview_lW5eq02uyQWDJiNGsxX901icN7Fl8AQ8SwMOpToG/mcp"
}
}
} - Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Accident Investigation Prover
Ask Copilot: "Using Accident Investigation Prover, help me...". 1 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"accident-investigation-prover": {
"url": "https://edge.vinkius.com/vk_preview_lW5eq02uyQWDJiNGsxX901icN7Fl8AQ8SwMOpToG/mcp"
}
}
} - Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Accident Investigation Prover
Open Cascade and ask: "Using Accident Investigation Prover, help me...". 1 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"accident-investigation-prover": {
"url": "https://edge.vinkius.com/vk_preview_lW5eq02uyQWDJiNGsxX901icN7Fl8AQ8SwMOpToG/mcp"
}
}
} - Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Accident Investigation Prover
Ask Cline: "Using Accident Investigation Prover, help me...". 1 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add accident-investigation-prover --transport http "https://edge.vinkius.com/vk_preview_lW5eq02uyQWDJiNGsxX901icN7Fl8AQ8SwMOpToG/mcp" - Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Accident Investigation Prover
Ask Claude: "Using Accident Investigation Prover, show me...". 1 tools are ready
Where the request belongs
Work Accident Investigation Prover can move forward.
This is for safety professionals who can't afford a 'pilot error' headline that ignores a systemic maintenance failure. It's for investigators who need to meet ICAO standards without manually checking every data point first.
Aviation Safety Manager
Auditing airline safety reports to ensure they aren't just checking boxes and actually address root causes.
Accident Investigator
Building a multi-causal narrative for a formal NTSB or ICAO report by correlating flight data with organizational records.
Regulatory Compliance Officer
Verifying that an operator's response to an incident actually addresses the systemic pressures identified in the investigation.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsFlight Risk Assessment Prover
A dispatch office cleared a flight into known CB activity with 'proceed with caution.' The crew never returned. Flight Risk Prover forces ICAO SMS-level threat identification with METAR data, 5×5 risk quantification, Swiss Cheese barrier modeling, SHELL/IMSAFE human factors analysis, and explicit GO/NO-GO commitment. eliminating the sycophantic go-bias that kills in aviation.
FMCSA SaferWeb (Carrier Safety)
Access real-time FMCSA carrier safety records, USDOT data, and inspection snapshots directly from the SAFER system.
IATA Developer Portal
Access aviation reference data. audit airports, airlines, and aircraft via AI.
Incident Postmortem Prover
Most postmortems fail: vague timelines, symptom-level root causes, and action items with no owner. This capability 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.
Boeing Developer Tools
Global aviation intelligence, Jeppesen aerodromes, and aircraft models.
OpenSky
Access real-time and historical global flight tracking data. monitor aircraft states, flight trajectories, and airport traffic directly from your AI agent.
Bring your own AI
Change the model, client or framework. Keep Accident Investigation Prover connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Accident Investigation Prover.
The practical details behind the request, access and result.
How does Accident Investigation Prover help with aviation safety?
It forces your AI to follow ICAO Annex 13 standards, ensuring you don't miss systemic issues like maintenance logs or organizational pressures.
Can this capability help me find the root cause of a flight incident?
Yes, it uses Reason's Model and the HFACS taxonomy to trace active failures back to latent conditions like budget constraints or training gaps.
Does Accident Investigation Prover check FDR and CVR data?
It requires the AI to correlate FDR parameters and CVR transcripts with ATC tracks and maintenance records before it'll allow a conclusion.
Will this help me write better safety recommendations?
It rejects vague goals like 'improve training' and forces the agent to write specific, measurable, and evidence-linked actions for named authorities.
Is Accident Investigation Prover suitable for NTSB-style reports?
Yes, it's built specifically to enforce the rigor required by NTSB and ICAO for multi-causal accident analysis.
Can I use Accident Investigation Prover to audit airline maintenance?
It can help you analyze MEL deferral rates and component life limits to see if they contributed to a specific incident.
How does this prevent 'pilot error' as a root cause conclusion?
The engine maintains a semantic trap list of blame-language signals: 'pilot error,' 'crew error,' 'human error,' 'judgment error,' 'failed to,' 'negligence.' If the LLM uses any of these in the HFACS taxonomy field, the classification is rejected. Instead, the LLM must classify each factor at the correct HFACS level: Level 1 (what the pilot did. skill error, decision error, perceptual error, or violation), Level 2 (what conditions enabled it. fatigue, CRM failure, environment), Level 3 (what supervision allowed it. scheduling, training gaps), Level 4 (what organizational decisions created it. budget cuts, staffing, regulatory gaps). 'Pilot error' is Level 1 only. the investigation must reach Level 4.
What evidence sources must be cross-referenced?
Five mandatory sources: (1) Flight Data Recorder. minimum 88 parameters per ICAO Annex 6, with timestamps. (2) Cockpit Voice Recorder. last 2 hours of audio, transcribed with timestamps, correlated with FDR parameter changes. (3) ATC recordings. radar track, clearances, handoffs, weather advisories. (4) Maintenance logs. last A/B/C/D checks, MEL items, deferred defects, AD compliance, component life (TSN/TSO/CSN/CSO). (5) Wreckage analysis. impact signatures, fire patterns, fracture analysis (fatigue vs overload), metallurgical examination. The engine rejects speculative language like 'it appears that' or 'evidence suggests' when hard data from these sources exists.
Why does this require recommendations to be addressed to specific authorities?
Because 'improve training' with no addressee has zero accountability. The NTSB model requires each recommendation to name the authority responsible for implementation. the FAA, the operator, the manufacturer, or an international body. Each recommendation must include: what specific action to take, measurable success criteria, a response deadline (typically 90 days), a verification mechanism (audit, inspection, data review), and a direct link to a specific investigation finding. This is how aviation achieved its extraordinary safety record. not through vague wishes, but through tracked, accountable, evidence-linked changes.
One connection away
Give your agent a direct line to Accident Investigation Prover.
Connect Accident Investigation Prover once. Keep it beside 5,900+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available