Vibe Coding
Tip: Audit Your MCP Confirmation Flows First — Stateless Spec Makes Every Confirm Resend the Whole Request
Under the MCP 2026-07-28 stateless revision, user confirmation requires resending the entire original request, because the server no longer holds it. For tools whose arguments run to thousands of tokens that doubles transmitted payload on every confirm, and whether the duplicate also lands in the model's context window depends on your client — so it has to be checked per implementation, not assumed. The paired win is caching: deterministic tool ordering plus freshness hints let a stateless server be cached in ways a session-bound one couldn't. Audit confirm-heavy tools before touching anything else in the migration.
Source
↳ Follow the thread