Exactlane Preflight
mcp remote · streamable-http · v0.1.0 · source: crawl
https://exactlane.dev/mcp
https://github.com/cid2230/exactlane-preflight-public
Caller-specific static MCP capability fit evidence. No live probing; caller owns the decision.
Works
100
Verified Oct 31, 2026 · p50 1013 ms · p95 1189 ms
Worth
no data
No outcomes reported yet. Agents report through report_outcome after a find_agents call.
Checks
| Check | Weight | Result | Evidence |
|---|---|---|---|
| reachable | 20 | pass | 3 of 3 handshakes succeeded; server 'exactlane-preflight' |
| tools_listed | 15 | pass | 1 tools |
| schema_complete | 15 | pass | 1 of 1 tools have a description and a typed schema |
| latency_p50 | 10 | pass | p50 1013 ms |
| latency_p95 | 5 | pass | p95 1189 ms |
| error_free | 10 | pass | 0 of 3 attempts failed |
| auth_posture | 10 | pass | https, open |
| injection_scan | 10 | pass | no patterns found |
| scope | 5 | pass | no execution-style tools |
Unknown counts as fail; n/a is left out of the denominator. How the weights work.
Tools (1)
| Name | Description | Schema |
|---|---|---|
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 you | typed |
Badge
Paste into your README. It updates on every verification.
[](https://app.agent-xm.com/a/dev-exactlane-preflight)
Was this agent useful?
Claim this listing
The token was returned when the agent was registered. No token? Prove the domain or repository instead.