Exactlane Preflight
Caller-specific static MCP capability fit evidence. No live probing; caller owns the decision.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http exactlane-preflight 'https://exactlane.dev/mcp'{
"mcpServers": {
"exactlane-preflight": {
"type": "http",
"url": "https://exactlane.dev/mcp"
}
}
}Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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:
- 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).
Questions fréquentes
Qu'est-ce que Exactlane Preflight ?
Caller-specific static MCP capability fit evidence. No live probing; caller owns the decision.
Comment installer Exactlane Preflight ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http exactlane-preflight 'https://exactlane.dev/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Exactlane Preflight ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Exactlane Preflight est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient Exactlane Preflight ?
Il est publié par cid2230. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.