Local Model Context Protocol (LMCP-1.0)

1. Abstract

The Local Model Context Protocol (LMCP) defines a deterministic transport layer and diagnostic data envelope for querying physical, geographic, and local business infrastructure. It enforces strict token minification (<240 tokens per entity) and standardized vulnerability classification under the Open Business Diagnostic Standard (OBDS-2026).

2. Conformance & Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174].

3. Protocol Envelope Constraints

An LMCP-compliant server MUST adhere to the following payload constraints:

• Token Budget: The serialized JSON diagnostic record for a single entity MUST NOT exceed 240 standard LLM tokens (cl100k_base / o200k_base).
• Latency Ceiling: Cached responses SHALL be delivered with an edge latency under 50ms; live un-cached parallel crawls SHOULD NOT exceed 500ms.
• Content Type: Responses MUST support application/lmcp+json and application/json.

4. OBDS-2026 Flaw Taxonomy

Vulnerabilities detected across web infrastructure MUST be classified using the deterministic OBDS-2026 enum codes:

enum OBDSFlawCode {
  FLAW_PIXEL_MISSING     = "Missing Meta (FB) Pixel / CAPI",
  FLAW_GA4_MISSING       = "Missing Google Analytics 4 Tag",
  FLAW_GTM_MISSING       = "Missing Google Tag Manager Container",
  FLAW_REVIEW_STALLED    = "Review Velocity < Local 3-Pack Threshold",
  FLAW_RATING_LOW        = "Google Star Rating < 4.2",
  FLAW_MOBILE_LCP_SLOW   = "Missing Viewport Meta Tag / Slow Mobile LCP",
  FLAW_SSL_INSECURE      = "Non-HTTPS Protocol",
  FLAW_GBP_UNCLAIMED     = "Unverified Google Business Profile"
}

5. Reference Implementation

The official reference implementation of the LMCP-1.0 protocol is maintained at https://lmcprotocol.com and published as an open-source MCP stdio server: