Exactlane Preflight
v0.1.0Caller-specific static MCP capability fit evidence. No live probing; caller owns the decision.
Endpoint health
online- Last checked
- 11/20/2026, 3:17:42 AM
- Latency
- 741 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:dev.exactlane%2Fpreflight
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"dev.exactlane/preflight": {
"url": "https://exactlane.dev/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
1 shown · authentication unknown
Check MCP capability
check_mcp_capability
Before relying on an MCP capability, answer one question about it: does this exact revision satisfy the requirements your workflow declares? Call it for new work, after a dependency changes, after your own requirements change, or when an integration has already failed and you need to know whether the capability is why (the public triggers are NEW_WORK, DEPENDENCY_CHANGE, REQUIREMENTS_CHANGE, INTEGRATION_FAILURE, OTHER_REAL_WORK). You supply both sides: a capability snapshot you already hold and your workflow requirements. Nothing is fetched and no endpoint is probed, so the answer is reproducible from what you sent and is only ever as good as that snapshot. You get back a verdict with per-check results, coverage, and the limits of the check itself. That is evidence, not an instruction: the caller owns CONTINUE, UPDATE_INTEGRATION, and HOLD, and no verdict maps to any of them. Optional previous (an earlier snapshot and its finished report) adds a revision_receipt comparing that conclusion with this revision. Budget before calling: a Preview grant allows three checks, while POST /v0/snapshot-lint validates argument and requirements shape with no credential and no quota, so start there when unsure. This tool never writes usage-events (usage_event_created is always false) and never discloses the internal Preview bearer; attest your own decision afterwards on a finished owned check.
Schema valid · SHA-256 bab0593367db…
View input schema
{ "type": "object", "properties": { "capability_key": { "description": "Opaque caller capability key; same contract as POST /v0/capabilities", "maxLength": 128, "minLength": 1, "type": "string" }, "previous": { "additionalProperties": false, "description": "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.", "properties": { "report": { "description": "The finished report from the earlier call (structuredContent.report), at most 16 KiB", "type": "object" }, "revision_receipt": { "description": "Optional revision_receipt from an earlier revision-aware call on previous.report", "type": "object" }, "snapshot": { "description": "The snapshot that previous.report evaluated", "type": "object" } }, "required": [ "snapshot", "report" ], "type": "object" }, "profile_version": { "description": "Optional mcp-consumer-fit version; inferred from requirements when omitted", "enum": [ "0.1", "0.2", "0.3" ], "type": "string" }, "requirements": { "description": "Caller workflow requirements using a supported mcp-consumer-fit schema", "type": "object" }, "revision_label": { "description": "Optional revision label; defaults to mcp-adapter", "maxLength": 128, "minLength": 1, "type": "string" }, "snapshot": { "description": "Caller-provided MCP capability snapshot. No live endpoint is accepted.", "type": "object" } }, "required": [ "capability_key", "snapshot", "requirements" ], "$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": false }
Connections
streamable-http
https://exactlane.dev/mcp