Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "preflight": {
      "type": "http",
      "url": "https://exactlane.dev/mcp"
    }
  }
}

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

[mcp_servers.preflight]
url = "https://exactlane.dev/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "preflight": {
      "type": "remote",
      "url": "https://exactlane.dev/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "preflight": {
      "type": "http",
      "url": "https://exactlane.dev/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=preflight&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZXhhY3RsYW5lLmRldi9tY3AifQ%3D%3D"
}

{
  "servers": {
    "preflight": {
      "type": "http",
      "url": "https://exactlane.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "preflight": {
      "httpUrl": "https://exactlane.dev/mcp"
    }
  }
}

extensions:
  "preflight":
    enabled: true
    name: "preflight"
    type: streamable_http
    uri: "https://exactlane.dev/mcp"
    timeout: 300

Quality 97 / 100strong

protocol100 · weight 25

pass
protocol.modernsupports 2026-07-28 (server/discover)
pass
protocol.statelessanswers without a session
pass
protocol.transportstreamable HTTP
pass
protocol.list_ttltool list is cacheable (ttlMs 3600000)

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene93 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations1 of 1 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 787 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

1 tools, about 787 tokens to load them all · tool set 97f151544ae7 · checked 2026-10-19 10:20 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 92 / 100

provenance85

liveness99

freshness85

hygiene100

+repository +dns-namespace +website +reachable +uptime-98% ~updated-38d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://exactlane.dev/mcp` streamable-http	none	yes	98%	849 ms	2026-07-28	2026-10-19

Tools (1)

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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "dev.exactlane/preflight",
  "_meta": {
    "io.modelcontextprotocol.registry/publisher-provided": {
      "stateless": true,
      "transport": "streamable-http",
      "adapter_only": true,
      "live_probing": false,
      "primary_tool": "check_mcp_capability",
      "protocol_revision": "2026-07-28"
    }
  },
  "title": "Exactlane Preflight",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://exactlane.dev/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "repository": {
    "url": "https://github.com/cid2230/exactlane-preflight-public",
    "source": "github"
  },
  "websiteUrl": "https://exactlane.dev",
  "description": "Caller-specific static MCP capability fit evidence. No live probing; caller owns the decision."
}