Your MCP server list now flags a rejected login token, and clears the warning once it recovers.
What's wrong with this entry?
A 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.
- Message directs you to run /login and then reconnect.
- A successful tools/list now clears discoveryAuthFailure in both MCP client implementations, so a recovered server stops showing the warning.
but your claude.ai session token was rejected. Run /login, then reconnect.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Remote Control tells you when a credential expired instead of just dropping
Both mention login
-
v2.1.224
Remote Control errors are typed as auth or terminal
Both mention login
-
v2.1.225
Remote Control re-arms itself after a re-login
Both mention login