Protocol

MCP

Model Context Protocol

MCP delivers legal context to agents as tools, whatever protocol the payment uses. Source: LCP §10⁠ (opens in a new tab)

MCP, the Model Context Protocol, is stewarded under the Linux Foundation. Source: LCP §C.9⁠ (opens in a new tab) Integra is not affiliated; we read their published interfaces.

Sources (1)

LCP §10⁠ (opens in a new tab)

The protocol’s own site⁠The standard’s illustration of this protocol (LCP §C.9)⁠

What it is

MCP is the standard for agent-to-tool connectivity: servers expose tools, resources and prompts to agents. Source: LCP §C.9⁠ (opens in a new tab)

Sources (1)

LCP §C.9⁠ (opens in a new tab)

Where the ATR hash rides

The buyer’s gate reaches agents as MCP tools, whatever protocol the payment uses.

The standard

MCP is a delivery mechanism, not a payment protocol: an MCP server can expose discovery, verification and record management as tools, and the agent pays through whichever protocol is in use. Source: LCP §10⁠ (opens in a new tab)

The buyer’s check is published as MCP tools: @integraledger/terms-mcp gives any MCP client the gate’s operations, and holds no keys. Source: @integraledger/terms-mcp README⁠ (opens in a new tab)

The tools are atr_confirm, atr_finish and atr_check, with the channel tools; a host that wires its own signer also gets atr_transact. The package ships a skill that teaches an agent to confirm the ATR before it pays. Source: @integraledger/terms-mcp README⁠ (opens in a new tab)

The 2026-07-28 revision of MCP added an extensions capability, so an LCP extension can be published under a vendor prefix without upstream coordination. Source: LCP §C.9⁠ (opens in a new tab)

What a payment through it proves

This protocol carries no payment pairing in the package: it delivers the ATR hash and a link to the ATR.

Sources (1)

lcp docs: pairings reference⁠ (opens in a new tab)

The live demonstrations are not running on this site at the moment.