Protocol compatibility

MCP 2026-07-28

This is the preferred protocol. The Lattix server supports stateless per-request context, server/discover, private cache hints for discovery and tool lists, and the input-required flow used to confirm writes.

Each request must carry the MCP 2026-07-28 protocol envelope and matching HTTP method metadata. There is no initialization session to authorize or keep alive; authentication and tenant context are validated for every HTTP request.

MCP 2025-11-25

The compatibility path is stateless and supports the legacy initialize and tool-call shapes. It does not create durable server sessions. Legacy write calls fail closed until the client repeats the operation with confirmed: true after user review.

Compatibility does not weaken OAuth audience checks, tenant binding, mTLS, scope enforcement, input limits, rate limits, or downstream token exchange.

Client guidance

• Prefer MCP 2026-07-28 for new integrations.
• Treat protocol-negotiation errors as configuration failures; do not silently downgrade to an unlisted revision.
• Refresh discovery and tool metadata according to the server's private cache hints.
• Do not persist or share one tenant's tool responses with another tenant.