Know whether your MCP actually works.

FlightCheck probes the complete read-only handshake, measures tool-schema weight, and flags compatibility risks before your users find them in Claude, Codex, ChatGPT, Cursor, or VS Code.

Run a free check Explore the AI toolkit
  • No advertised tools are invoked
  • Credentials are used only for this scan
  • Private-network targets are blocked
flightcheck
01initializepass
02notifications/initialized202
03tools/list47 tools
04schema budget8,412 tokens
05hosted client probes2 warnings
Compatibility signal92/100

Scan a public Streamable HTTP endpoint

Use the runtime URL—not its .well-known metadata URL. Ports are limited to 80 and 443 for public-scan safety.

Temporary authentication header

The value is sent only to the endpoint during this scan. It is not included in the report or saved by FlightCheck.

Compliance is not compatibility.

An endpoint can return HTTP 200 and still fail in a hosted client because optional probes, notifications, session headers, content blocks, and authentication discovery are handled differently. FlightCheck makes those edges visible.

1

Probe

Exercise the read-only handshake and discovery surface.

2

Profile

Compare the evidence with strict and client-family expectations.

3

Repair

Get concrete recommendations tied to failing protocol behavior.