Skip to content

Exactlane Preflight

by exactlane.dev · remote · no sign-in to list tools · v0.1.0 · published by dev.exactlane

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

Changes · 1
CompareRegistry entry

1 tool: 1 change things.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http preflight https://exactlane.dev/mcp

Findings

Matches of fixed checks, with the text they matched.

1 info

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Changes things 1Claude Code: ask
  • check_mcp_capabilityBefore relying on an MCP capability, answer one question about it: does this exact revision satisfy the requirements your workflow declares?1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...argument and requirements shape with no credential and no quota, so start there when unsur..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
    • readOnlyHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http preflight https://exactlane.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__preflight__check_mcp_capability"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as preflight. Review it before you use it.