MCP sign-ins are bound to one server, and a reused refresh token ends them
A client that names the MCP server it wants when it signs in (Claude and ChatGPT do) gets access that works on that server alone: the team's Apps server's reaches each environment's under it, an environment's reaches that environment, and Inference Bureau's own server reaches itself. Account → Sessions says which server each signed-in app has.
A connector's refresh token works once. One presented again after it was replaced means it was copied, so the sign-in ends for everyone holding it and the team's audit log records it. A client retrying a refresh whose answer it never received, within a few seconds, is unaffected.
An MCP client can now name itself with the address of its client ID metadata document instead of registering, as ChatGPT prefers and Claude Code does. The approval page reads the document, shows the name it gives, and refuses a sign-in whose return address the document doesn't list.
More in Signing in.