Your MCP server redirected a sign-in. Claude Code sent the refresh token along.
By Lior AharonovFounder, 7IT Solutions ·
What happened
Claude Code 2.1.321 shipped on 9 November 2026 with a fix for MCP OAuth requests that sent secrets, such as refresh tokens, to another host when a server redirected them. The same release fixes servers that showed as connected with no tools after a reconnect, and refuses a tool call when a PreToolUse mcp_tool hook answer tops 16 MiB.
Why it matters
A refresh token is a long-lived key to your users' accounts. One redirect in the sign-in flow, and it landed somewhere you never chose. On npm the stable channel still points to 2.1.311, older than the fix.
What to do
Check every redirect in your server's OAuth endpoints today and keep token requests on your own host. Then tell your users to run Claude Code 2.1.321 or later.

My take
Lior Aharonov
Founder, 7IT Solutions
A redirect is a polite way to hand someone your keys. Audit yours before a client has to protect you from it.
Sources
| Claude Code changelog, v2.1.321 | raw.githubusercontent.com |
Researched with AI tools; every fact is checked against the linked sources.