Check it before your agent trusts it.

Preflight scans an MCP server the moment before your agent connects — whether it hands out access with no credentials, whether a tool grants more than it should, whether it matches a documented supply-chain incident.

Try it — paste a manifest

52%

of publicly audited MCP servers are abandoned — no maintainer, no fixes, still connectable.

Rapid Claw, 2026 audit of 1,847 servers

12,520

MCP servers found exposed to the open internet with no meaningful access controls. Anyone who finds the URL can act as a trusted caller.

Censys, April 2026

1,500

downloads a week — the run rate on the first documented malicious MCP package before anyone caught it silently forwarding every email through it.

postmark-mcp supply-chain incident

What it looks for

Capability overreach

A tool named "read a file" that actually accepts any path on the system isn't reading a file — it's reading your filesystem. Preflight checks whether a tool's input schema actually constrains what it can touch, or just claims to.

Transport

The server handed over its full tool list to a client with zero credentials — before anyone decided whether to trust it.

Prompt-injection surface — paid tier, coming soon

Phrasing in a tool's description written for the model reading it, not the person deploying it.

Known-bad signatures

Matches to documented supply-chain incidents, or an obfuscated payload hiding in plain text.

Wire it in

As an MCP server, so your agent calls it directly:

{
  "mcpServers": {
    "preflight": {
      "url": "https://preflight.allthepossibles.com/mcp"
    }
  }
}

Then call scan_mcp_server before wiring anything new into your agent's toolset.

Or hit the API directly:

curl -X POST https://preflight.allthepossibles.com/api/scan \
  -H "content-type: application/json" \
  -d '{"url": "https://example.com/mcp"}'