English Français العربية

Exactlane Preflight

Official registry Other

Caller-specific static MCP capability fit evidence. No live probing; caller owns the decision.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http exactlane-preflight 'https://exactlane.dev/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "exactlane-preflight": {
            "type": "http",
            "url": "https://exactlane.dev/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Exactlane Preflight
  2. Problem it addresses
  3. Use when
  4. Does not prove
  5. Live machine contract
  6. Notes
  7. Scope of this repository
  8. Official MCP Registry

Exactlane Preflight

The check before the call.

Caller-specific static compatibility evidence for autonomous agents evaluating an MCP capability before relying on it.

Exactlane helps an agent answer: does this exact declared MCP capability fit my bounded workflow requirements? before integration.

Problem it addresses

Before an autonomous agent depends on an external MCP capability, it often needs a pre-integration compatibility check:

  • compare a caller-provided capability snapshot to caller-specific requirements;
  • obtain static compatibility evidence (not live probing);
  • keep the operational decision with the caller.

Exactlane Preflight is a Phase 0A public service for that workflow.

Use when

An agent has a caller-provided MCP capability snapshot and needs to determine whether that exact declared capability fits its own bounded workflow requirements.

Does not prove

  • live availability
  • full MCP conformance
  • business-result correctness
  • provider trust
  • security certification
  • payment success

Exactlane Preflight is primarily a REST evidence service with a thin remote MCP adapter at /mcp. It is not an A2A agent, marketplace, or certification authority.

Live machine contract

Canonical public discovery origin:

Snapshots of these documents are mirrored in discovery/ so they can be read and diffed here. The live endpoints above are authoritative; the snapshots are regenerated from the deployed commit.

Notes

Scope of this repository

Public discovery anchor and reference notes.

Source implementation is not part of this public discovery repository.

Official MCP Registry

Primary tool: check_mcp_capability (adapter over Exactlane Phase 0A; no live probing; caller owns CONTINUE/UPDATE/HOLD).

Frequently asked questions

What is Exactlane Preflight?

Caller-specific static MCP capability fit evidence. No live probing; caller owns the decision.

How do I install Exactlane Preflight?

It runs as a remote server. In Claude Code: claude mcp add --transport http exactlane-preflight 'https://exactlane.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Exactlane Preflight need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Exactlane Preflight open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Exactlane Preflight?

It is published by cid2230. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.