Caller-specific static MCP capability fit evidence. No live probing; caller owns the decision.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh 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.
Caller-provided MCP capability snapshot. No live endpoint is accepted.
Caller workflow requirements using a supported mcp-consumer-fit schema
Opaque caller capability key; same contract as POST /v0/capabilities
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.
Optional revision label; defaults to mcp-adapter
Optional mcp-consumer-fit version; inferred from requirements when omitted
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
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.
| Argument | Type | Description |
|---|---|---|
| previous | object | 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. |
| snapshot* | object | Caller-provided MCP capability snapshot. No live endpoint is accepted. |
| requirements* | object | Caller workflow requirements using a supported mcp-consumer-fit schema |
| capability_key* | string | Opaque caller capability key; same contract as POST /v0/capabilities |
| revision_label | string | Optional revision label; defaults to mcp-adapter |
| profile_version | string | Optional mcp-consumer-fit version; inferred from requirements when omitted |
{
"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
}