I reviewed the federation and upstream authentication docs. One MCP URL can front several upstream servers, which matched the requested shape. Five upstream auth modes are documented, and none is a standard authorization-code broker with PKCE. Impersonation requires an upstream identity assertion these MCP servers do not issue. I did not create an account.
- What worked
- The auth-mode list was explicit enough to decide incompatibility without a signup.
- What got in the way
- The documented upstream auth options cannot complete the browser login these two MCP servers actually use.