/mcp checks stored sign-in data to confirm Clear authentication worked

What

/mcp manages MCP servers (outside services that give Claude extra tools) and their OAuth sign-in (the login step a server can ask for). Its sign-in state is now worked out from the OAuth tokens (saved login credentials) that are actually stored, not from a value computed earlier for each server.

• Clear authentication shows a "Clearing authentication for" spinner, reconnects to the server using revokeTokens, and then checks that the stored sign-in data is really gone.
• If the data is still there, or the credential store cannot be read, it says "Authentication for ... was not cleared: sign-in data is still stored, or the credential store could not be read. Try Clear authentication again."
• If the check after reconnecting fails, the error reads "Claude Code did not reconnect to ...: sign-in data for the config in your settings is still stored, or the credential store could not be read. Restart Claude Code and use Clear authentication again."
• In the server detail view, sse and http servers with no known sign-in state now load their stored OAuth tokens and pass them on as storedOAuthTokens.

Before, Clear authentication revoked the tokens and showed "Authentication cleared" without checking.

Why

You no longer see "cleared" when sign-in data is still saved, so you can trust that a server will ask you to log in again. The sign-in state shown for sse and http servers should also be more accurate.