MCPサーバー

Exactlane Preflight

dev.exactlane/preflight
MCP・エージェント基盤 公開・接続可能 MCP 2025-11-25

このMCPでできること

Checks whether a supplied MCP capability snapshot satisfies workflow requirements without live probing.

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.
入力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['capability_key', 'snapshot', 'requirements'], 'properties': {'previous': {'type': 'object', 'required': ['snapshot', 'report'], 'properties': {'report': {'type': 'object', 'description': 'The finished report from the earlier call (structuredContent.report), at most 16 KiB'}, 'snapshot': {'type': 'object', 'description': 'The snapshot that previous.report evaluated'}, 'revision_receipt': {'type': 'object', 'description': 'Optional revision_receipt from an earlier revision-aware call on previous.report'}}, '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.', 'additionalProperties': False}, 'snapshot': {'type': 'object', 'description': 'Caller-provided MCP capability snapshot. No live endpoint is accepted.'}, 'requirements': {'type': 'object', 'description': 'Caller workflow requirements using a supported mcp-consumer-fit schema'}, 'capability_key': {'type': 'string', 'maxLength': 128, 'minLength': 1, 'description': 'Opaque caller capability key; same contract as POST /v0/capabilities'}, 'revision_label': {'type': 'string', 'maxLength': 128, 'minLength': 1, 'description': 'Optional revision label; defaults to mcp-adapter'}, 'profile_version': {'enum': ['0.1', '0.2', '0.3'], 'type': 'string', 'description': 'Optional mcp-consumer-fit version; inferred from requirements when omitted'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', '$schema': 'https://json-schema.org/draft/2020-12/schema', 'required': ['report', 'caller_owns_operational_decision', 'usage_event_created'], 'properties': {'report': {'type': 'object', 'description': 'Finished Exactlane check report, substantially unchanged'}, 'decision_note': {'type': 'string'}, 'revision_receipt': {'type': 'object', 'description': 'Present only when previous was supplied: exactlane.revision-receipt/0.1. The global previous-to-current comparison is authoritative; isolated change evaluations report DIRECT_EFFECT_OBSERVED, NO_ISOLATED_EFFECT_OBSERVED or NOT_EVALUATED and cannot rule out interaction effects.'}, 'usage_event_created': {'type': 'boolean', 'const': False, 'description': 'Always false. check_mcp_capability does not POST /v0/usage-events and does not disclose the internal Preview bearer. To attest a client-owned CONTINUE, UPDATE_INTEGRATION, or HOLD decision, use REST POST /v0/usage-events after a finished owned check; report_consumed is required.'}, 'caller_owns_operational_decision': {'type': 'boolean', 'const': True}}, 'additionalProperties': False}
追加
check_mcp_capability
2026年9月29日2:49