Legal Context ProtocolIANA Considerations
Well-known URI registration for the LCP discovery endpoint.
This specification requests the registration of a well-known URI per RFC 8615. As of the date of this document no entry for legal-context.json exists in the IANA Well-Known URIs registry; the table below states the registration sought, not one that has been granted.
| Field | Value |
|---|---|
| URI suffix | legal-context.json |
| Change controller | LCP Technical Steering Committee |
| Specification document | This document |
| Status | Intended — provisional registration sought; not yet filed |
| Related information | Provides legal context discovery for agentic commerce. Complements /.well-known/agent-card.json (A2A), which is registered permanent with the Linux Foundation as change controller. |
Registration is not a precondition for conformance.
MCP as Delivery Mechanism
An LCP MCP server is the natural delivery channel for legal context — protocol-independent and reachable by any MCP-compatible agent platform.
Security Considerations
Transport security, document integrity, terms versioning, ephemeral link security, privacy, rate limiting, and agent-side security considerations (prompt injection, autonomous signing, display-versus-signed divergence, replay across versions, signing-key compromise).