{"version":"2.1.221","anchor":"mcp-connection-dial-out-deduped-by-a-once-guard","canonical_anchor":"mcp-connection-dial-out-deduped-by-a-once-guard","heading":"MCP connection dial-out deduped by a once-guard","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/mcp-connection-dial-out-deduped-by-a-once-guard","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### MCP connection dial-out deduped by a once-guard\n\nMCP tool and command collection is less likely to hang or finish twice.\n\n**What**\n\nThe routine that walks connected clients to collect tools and commands now uses an explicit once-guard closure instead of counting callbacks against an expected total.\n\n**Details**\n\n- Completion can now fire from triggers other than the last callback without double-resolving.\n- Previously the count had to match exactly for the routine to settle.\n\n**Evidence**\n\n`ensureConnectedClient`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}