{"version":"2.1.222","anchor":"mcp-rejected-claude-ai-session-token-is-now-visible","canonical_anchor":"mcp-rejected-claude-ai-session-token-is-now-visible","heading":"MCP: rejected claude.ai session token is now visible","tier":"use","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/mcp-rejected-claude-ai-session-token-is-now-visible","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### MCP: rejected claude.ai session token is now visible\n\nYour MCP server list now flags a rejected login token, and clears the warning once it recovers.\n\n**What**\n\nA connected MCP server whose discovery bearer token was rejected now says so in the server list and in the reconnect result, rather than the state being tracked only internally.\n\n**Details**\n\n- Message directs you to run \/login and then reconnect.\n- A successful tools\/list now clears discoveryAuthFailure in both MCP client implementations, so a recovered server stops showing the warning.\n\n**Evidence**\n\n`but your claude.ai session token was rejected. Run \/login, then reconnect.`\n\n- Area: MCP\n- Names: `\/login`, `\/mcp`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 0\/5"}