{"version":"2.1.238","anchor":"mcp-reauth-gets-one-retry-per-connection-plus-two-test-hooks","canonical_anchor":"mcp-reauth-gets-one-retry-per-connection-plus-two-test-hooks","heading":"MCP reauth gets one retry per connection, plus two test hooks that are switched off","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/mcp-reauth-gets-one-retry-per-connection-plus-two-test-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### MCP reauth gets one retry per connection, plus two test hooks that are switched off\n\nSimultaneous MCP re-auth attempts now collapse into one retry instead of racing each other.\n\n**What**\n\nWhen an MCP server needs reauthenticating, concurrent attempts now collapse into a single in-flight retry that reports itself as `started`, `joined` or `stale_refused`, alongside new per-connection bookkeeping for superseded connection attempts and background refreshes. Two accompanying hooks exist only for tests and cannot be used here.\n\n**Details**\n\n- The setter that would keep a stale reauth entry around throws on any truthy value, so the behaviour it guards is unreachable in this build.\n- The hook for observing reauth decisions has no caller in the bundle and is read with optional chaining at two places, making it a no-op.\n\n**Evidence**\n\n`setHoldStaleReauthEntryForTest is test-only`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}