MCP

This section is advisory.

MCP is the universal standard for agent-to-tool connectivity (97M+ monthly downloads), governed by the AAIF under the Linux Foundation. See the full MCP as Delivery Mechanism section for detailed guidance on LCP as an MCP server.

Tool-Level Legal Context

MCP tools that involve legally significant actions (purchases, commitments, agreements) can signal this through their standard annotations and description. The destructiveHint and openWorldHint annotations indicate state-changing external interactions; the tool description should specify that legal context verification is expected before invocation:

{
  "name": "execute_purchase",
  "description": "Execute a purchase. Caller should verify legal context (LCP) before invocation.",
  "annotations": {
    "destructiveHint": true,
    "openWorldHint": true
  }
}

Tools annotated with both destructiveHint and openWorldHint are performing state-changing actions in the external world — exactly the kind of operations where legal context matters.

Full MCP Integration

For the complete LCP-as-MCP-server architecture — including tools (get_legal_context, verify_terms, accept_terms, create_agreement, initiate_dispute), resources (integra://legal-context/{domain}, integra://agreement/{id}), prompts, and deployment guidance — see MCP as Delivery Mechanism.