About Exactlane Preflight
Exactlane Preflight is a REST evidence service with a remote MCP adapter for agents checking whether a declared capability fits bounded workflow requirements. It provides static compatibility evidence, while the caller makes the operational decision.
Key features
- 01Caller-specific capability fit checks
- 02Static compatibility evidence
- 03REST service with remote MCP adapter
- 04Caller retains operational decision
Use cases
- 01Check a capability snapshot before integration
- 02Compare declared capabilities with workflow requirements
MCP support
A remote MCP adapter is available at `/mcp`, with `check_mcp_capability` as its primary tool. It returns static evidence and does not perform live probing.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://exactlane.dev/mcpclaude mcp add --transport http dev-exactlane-preflight https://exactlane.dev/mcp{"mcpServers":{"dev-exactlane-preflight":{"type":"http","url":"https://exactlane.dev/mcp"}}}Open in Cursor{"servers":{"dev-exactlane-preflight":{"type":"http","url":"https://exactlane.dev/mcp"}}}Open in VS Code{"mcpServers":{"dev-exactlane-preflight":{"type":"http","url":"https://exactlane.dev/mcp"}}}{"mcpServers":{"dev-exactlane-preflight":{"serverUrl":"https://exactlane.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
1| Parameter | Type | Required | Description |
|---|---|---|---|
| previous | object | No | Optional. Makes this a revision-aware check (POST /v0/revision-checks semantics). Send the snapshot and finished report from an earlier check of the same capability_key with identical requirements. Exactlane re-evaluates them instead of trusting the report and never looks up earlier calls. Omit for the ordinary check. |
| previous.report | object | Yes | The finished report from the earlier call (structuredContent.report), at most 16 KiB |
| previous.snapshot | object | Yes | The snapshot that previous.report evaluated |
| previous.revision_receipt | object | No | Optional revision_receipt from an earlier revision-aware call on previous.report |
| snapshot | object | Yes | Caller-provided MCP capability snapshot. No live endpoint is accepted. |
| requirements | object | Yes | Caller workflow requirements using a supported mcp-consumer-fit schema |
| capability_key | string | Yes | Opaque caller capability key; same contract as POST /v0/capabilities |
| revision_label | string | No | Optional revision label; defaults to mcp-adapter |
| profile_version | enum | No | Optional mcp-consumer-fit version; inferred from requirements when omitted0.1 | 0.2 | 0.3 |
Details
From the project READMEExactlane 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:
- Service root: https://exactlane.dev/
- Manifest: https://exactlane.dev/.well-known/exactlane.json
- OpenAPI: https://exactlane.dev/openapi.json
- Agent discovery text: https://exactlane.dev/llms.txt
- Sitemap: https://exactlane.dev/sitemap.xml
- Remote MCP: https://exactlane.dev/mcp
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
- MCP tool schemas that are valid on one side and unusable on the other: sourced cases where hosts or clients silently drop or reject tool schemas, and what Preflight can and cannot check about them.
Scope of this repository
Public discovery anchor and reference notes.
Source implementation is not part of this public discovery repository.
Official MCP Registry
- Server name:
dev.exactlane/preflight - Version:
0.1.0 - Remote: Streamable HTTP
https://exactlane.dev/mcp - Registry search: https://registry.modelcontextprotocol.io/v0.1/servers?search=exactlane
Primary tool: check_mcp_capability (adapter over Exactlane Phase 0A; no live probing; caller owns CONTINUE/UPDATE/HOLD).
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.