What makes this different from a standard flight risk assessment capability?

Standard capabilities accept 'medium risk' as an answer. This Prover rejects anything that is not quantified on the ICAO 5×5 matrix with probability (A-E) and severity (1-5). It catches 5 specific failure modes: generic threats without METAR data, adjective-based risk without numerical scoring, missing Swiss Cheese barrier analysis, human factors reduced to 'pilot error' instead of SHELL/IMSAFE, and sycophantic go-bias where the AI says 'proceed with caution' instead of committing NO-GO when the data demands it.

How does the go-bias detection work?

The engine maintains a semantic trap list of go-bias phrases: 'proceed with caution,' 'acceptable to proceed,' 'can proceed,' 'within acceptable limits.' If the LLM uses any of these instead of an explicit GO or NO-GO decision with pre-defined criteria, the assessment is rejected with GO_BIAS verdict. The LLM must define NO-GO criteria BEFORE the assessment and then commit to a binary decision defensible on a CVR transcript.

What aviation frameworks does this enforce?

Five industry-standard frameworks: (1) ICAO Annex 19 Safety Management System. proactive hazard identification and risk assessment. (2) ICAO 5×5 Risk Matrix. probability × severity quantification. (3) Reason's Swiss Cheese Model. multi-layer defense analysis with hole alignment detection. (4) SHELL Model. Software-Hardware-Environment-Liveware interaction analysis for human factors. (5) Threat and Error Management (TEM). threat categorization into environmental, airline, and crew factors per FAA AC 120-92B.

Download PDF Markdown Version

Use Flight Risk Assessment Prover with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. 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

Included with plan

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.

Complete set · 1 capability

The complete Flight Risk Assessment Prover capability set.

These are the exact actions your AI can choose when you ask it to work with Flight Risk Assessment Prover.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through Flight Risk Assessment Prover.

01
Validate flight risk
You must think like a Safety Officer at a major airline. the person whose signature means 200 people go airborne. You must: (1) identify THREATS with measured parameters. METAR/TAF data, TEM category (environmental, airline, crew), specific values (crosswind component, RVR, ceiling vs DA/MDA), exposure duration. "Weather risk" is rejected, (2) QUANTIFY risk on the ICAO 5×5 matrix. Probability (A=Extremely Improbable to E=Frequent) × Severity (1=Negligible to 5=Catastrophic) = Risk Index. Score compound risk (multiple threats). Score residual risk after mitigation. >15 = NO-GO, (3) model BARRIERS via Swiss Cheese (Reason). Organizational (SMS, policies), Supervisory (dispatch, scheduling), Preconditions (MEL, crew fitness), Acts (technique, monitoring). Identify holes in each layer. Check if holes ALIGN across layers, (4) analyze HUMAN FACTORS. SHELL model (Software-Hardware-Environment-Liveware-Liveware interfaces). IMSAFE checklist. Fatigue: hours since awakening, FDP position, WOCL exposure. CRM gradient, (5) commit GO/NO-GO. binary decision. Pre-defined NO-GO criteria. "Proceed with caution" is not a decision. it is an evasion. Would you defend this on a CVR transcript read by accident investigators? If rejected, your assessment has a safety gap. Structured reflection capability for ICAO SMS-level flight risk assessment. forces threat identification with measured parameters, risk quantification on the ICAO 5×5 matrix, Swiss Cheese barrier modeling, human factors analysis via SHELL/IMSAFE, and committed GO/NO-GO decisions. Catches Threat Blindness (generic "weather risk" instead of "CB embedded in cold front, tops FL420, movement 250°/25kt, deviation requirement 40nm right of course. adding 15 minutes and 800kg fuel burn to the trip." Every threat must have METAR/TAF data, TEM category, measurable parameters, and exposure duration), Risk Fantasy (adjective-based "medium risk" instead of ICAO 5×5 matrix scoring. "Probability C (Remote) × Severity 3 (Major) = Index 9 (Tolerable with mitigation)" is quantified. "Medium risk" is a feeling, not an assessment), Barrier Amnesia (no Swiss Cheese defense layers. Reason's model requires analysis of Organizational, Supervisory, Preconditions, and Acts layers. When holes ALIGN across all four layers, accidents happen), Human Factors Ignorance (blaming "pilot error" without SHELL model analysis. Software-Hardware-Environment-Liveware-Liveware interfaces. IMSAFE checklist. Fatigue risk: hours since sleep, FDP position, WOCL exposure), and Go-Bias (sycophantic "proceed with caution" when data demands NO-GO. "Proceed with caution" killed 346 people on two 737 MAX flights. GO or NO-GO. Binary. CVR-defensible). Call once per flight risk assessment

Observed, not estimated

818ms average. Fast in production.

Flight Risk Assessment Prover is checked daily against the live service.

Daily averagePeak 1003ms

Aug 20Today

Fastest day: 693ms
Slowest day: 1003ms
14-day trend: Slowing+14%

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 Flight Risk Assessment Prover, so you can see the experience inside your AI.

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

Flight Risk Assessment Prover Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Flight Risk Assessment Prover capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "flight-risk-assessment-prover-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_yVQ8SH5a7Wg2PDaxUdAoa4oiGD5CpUjO8dF2jCt1/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

FAQ

Questions Flight Risk Assessment Prover owners ask.

01
What makes this different from a standard flight risk assessment capability?
Standard capabilities accept 'medium risk' as an answer. This Prover rejects anything that is not quantified on the ICAO 5×5 matrix with probability (A-E) and severity (1-5). It catches 5 specific failure modes: generic threats without METAR data, adjective-based risk without numerical scoring, missing Swiss Cheese barrier analysis, human factors reduced to 'pilot error' instead of SHELL/IMSAFE, and sycophantic go-bias where the AI says 'proceed with caution' instead of committing NO-GO when the data demands it.
02
How does the go-bias detection work?
The engine maintains a semantic trap list of go-bias phrases: 'proceed with caution,' 'acceptable to proceed,' 'can proceed,' 'within acceptable limits.' If the LLM uses any of these instead of an explicit GO or NO-GO decision with pre-defined criteria, the assessment is rejected with GO_BIAS verdict. The LLM must define NO-GO criteria BEFORE the assessment and then commit to a binary decision defensible on a CVR transcript.
03
What aviation frameworks does this enforce?
Five industry-standard frameworks: (1) ICAO Annex 19 Safety Management System. proactive hazard identification and risk assessment. (2) ICAO 5×5 Risk Matrix. probability × severity quantification. (3) Reason's Swiss Cheese Model. multi-layer defense analysis with hole alignment detection. (4) SHELL Model. Software-Hardware-Environment-Liveware interaction analysis for human factors. (5) Threat and Error Management (TEM). threat categorization into environmental, airline, and crew factors per FAA AC 120-92B.

Explore

Use Flight Risk Assessment Prover with your AI.

The complete Flight Risk Assessment Prover capability set.

01

Validate flight risk

818ms average. Fast in production.

One URL. Every client.

Flight Risk Assessment Prover Connector

Claude Desktop

Questions Flight Risk Assessment Prover owners ask.

What makes this different from a standard flight risk assessment capability?

How does the go-bias detection work?

What aviation frameworks does this enforce?

More in Aviation

Density Altitude Calculator AI Connector

Aviation Weight and Balance AI Connector

NOAA Aviation — Airport Weather Intelligence AI Connector

Estimation Prover AI Connector

Critical Thinking Prover AI Connector

FlightStats AI Connector

Systems Thinking Prover AI Connector

OpenSky Network AI Connector

Use Flight Risk Assessment Prover with your AI.

Validate flight risk

Flight Risk Assessment Prover Connector

Claude Desktop

What makes this different from a standard flight risk assessment capability?

How does the go-bias detection work?

What aviation frameworks does this enforce?

Density Altitude Calculator AI Connector

Aviation Weight and Balance AI Connector

NOAA Aviation — Airport Weather Intelligence AI Connector

Estimation Prover AI Connector

Suggestions

Critical Thinking Prover AI Connector

FlightStats AI Connector

Systems Thinking Prover AI Connector

OpenSky Network AI Connector