NestDaddy

Exactlane Preflight

dev.exactlane/preflight · v0.1.0

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

Connect Remote server

Terminal
claude mcp add --transport http preflight https://exactlane.dev/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "preflight": {
      "url": "https://exactlane.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "preflight": {
      "type": "http",
      "url": "https://exactlane.dev/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://exactlane.dev/mcp

Tools 1 found in our last check

  • 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 ne…

Details

Endpointhttps://exactlane.dev/mcp (Streamable HTTP)
First published11 Sep 2026
Last updated11 Sep 2026
Registry namedev.exactlane/preflight

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.