Agent Capability Purchase Preflight Receipt MCP

A local evidence tool for comparing buyer-supplied AI capability offers before a human purchase decision. It blocks explicit policy conflicts, preserves incomplete feature fit for review and selects only a unique lowest-price eligible offer from the supplied manifests.

What it creates

• result.json
• capability-matrix.csv
• issues.jsonl
• CAPABILITY_PREFLIGHT.md
• evidence-receipt.json

Requirements

• Windows 11
• Python 3.11–3.14
• An MCP-compatible client
• MCP_LICENSE_KEY from the MCP Marketplace purchase
• Internet access for initial and periodic license verification

License verification sends only the license key and public product slug. Buyer evidence paths, contents and generated reports remain local.

Install from a purchased source checkout

python -m venv .venv
.\.venv\Scripts\python.exe -m pip install .

MCP client configuration

{
  "mcpServers": {
    "agent-capability-preflight": {
      "command": "agent-capability-preflight-mcp",
      "env": {"MCP_LICENSE_KEY": "PASTE_THE_KEY_FROM_YOUR_PURCHASE"}
    }
  }
}

Run the client from the folder containing buyer-authorized evidence. All supplied paths must be relative to that folder.

Tool

build_capability_purchase_preflight

• capabilities_path: Capability-offer JSONL
• policy_path: Owner policy JSON
• requirements_path: Required-feature JSON
• output_directory: new output directory

The tool returns structured JSON. ERROR means the request could not be processed.

CLI

The diagnostic command is unlicensed:

agent-capability-preflight --json doctor

Protected commands verify the marketplace license before reading buyer files:

agent-capability-preflight --json analyze --capabilities examples/sample-input/capabilities.jsonl --policy examples/sample-input/policy.json --requirements examples/sample-input/requirements.json --out packet
agent-capability-preflight --json show packet/result.json
agent-capability-preflight --json verify packet/evidence-receipt.json

Product boundary

It does not discover vendors, make payments, install products, authenticate accounts, invoke capabilities or verify vendor claims. All accepted evidence stays local. Apart from license verification, the package performs no network activity and has no telemetry.