Why one MCP endpoint needs separate control and data planes
A technical note on stable client contracts, identity, policy, routing, and portable deployment.
Engineering updates
Architecture, security, and operations in public.
This publication will document the decisions behind LiteMCP Composer, compatibility findings, release evidence, security changes, and the work required to operate a portable MCP control plane.
Policy must shape discovery and execution
The reason a deny decision has to apply before a capability is listed and again before it runs.
What complete self-hosting actually requires
Beyond a Helm install: preflight, identity, vaults, backup, upgrade, rollback, and diagnostics.
The update structure is live; individual posts are not presented as published until their technical review and evidence links are complete.