{"version":"2.1.259","anchor":"mcp-cold-start-now-waits-for-a-second-unverified-cache-conf","canonical_anchor":"mcp-cold-start-now-waits-for-a-second-unverified-cache-conf","heading":"MCP cold-start now waits for a second, unverified-cache confirmation stage","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/mcp-cold-start-now-waits-for-a-second-unverified-cache-conf","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### MCP cold-start now waits for a second, unverified-cache confirmation stage\n\nMCP cold start now waits for remote managed-settings confirmation when org MCP servers are withheld from the cache.\n\nMCP cold start now has an added wait stage for a case where `managedMcpServers` is withheld from the unverified cache: it logs a wait on remote managed-settings confirmation and awaits the settled-fetch promise before falling back to the older managed-settings-load check. A parallel code path gained the same fallback.\n\n- Area: MCP\n- Names: `managedMcpServers`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}