{"version":"2.1.280","anchor":"mcp-server-ownership-lease-released-with-a-gapcap-backoff","canonical_anchor":"mcp-server-ownership-lease-released-with-a-gapcap-backoff","heading":"MCP server ownership lease released with a gap\/cap backoff","tier":"internal","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/mcp-server-ownership-lease-released-with-a-gapcap-backoff","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### MCP server ownership lease released with a gap\/cap backoff\n\nMCP server ownership leases now release with a timed backoff instead of immediately\n\n**Unclear.** The exact events that trigger this release, and the precise effect of the gap\/cap values, are not detailed in the evidence.\n\n**What**\n\nClaude Code now releases an MCP server's ownership lease (a claim on managing that server's registration) using a backoff pattern with an 8000ms gap and a 60000ms cap, rather than releasing it immediately when certain events occur.\n\n**Why**\n\nPacing how quickly ownership of an MCP server registration can be released and reclaimed likely helps avoid rapid churn or conflicts when multiple processes are involved.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}