{"version":"2.1.321","anchor":"mcp-oauth-flow-now-runs-two-pre-checks-before-starting","canonical_anchor":"mcp-oauth-flow-now-runs-two-pre-checks-before-starting","heading":"MCP sign-in runs two extra checks before it starts","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/mcp-oauth-flow-now-runs-two-pre-checks-before-starting","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### MCP sign-in runs two extra checks before it starts\n\nMCP OAuth sign-in now runs two checks before the consent step, and reports a cancellation if one fails after you cancel\n\n**Unclear.** What the two new checks look at, and so when they stop a sign-in, is not known.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools, and some need you to sign in through OAuth, a standard sign-in flow. Before that sign-in begins, Claude Code now runs two extra checks using the server's name and settings.\n\nIf one of these checks fails after the sign-in has been cancelled, Claude Code reports that the sign-in was cancelled rather than the check's own error.\n\n**Why**\n\nMCP sign-in can now stop earlier, before any browser step.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}