tin-berri f6eaca9069 fix(mcp): serve token-forwarding servers when oauth discovery fails (#37399) ... true_passthrough and oauth_delegate forward the caller's own bearer and mint nothing, so their sessions consume no discovered OAuth endpoint. The discovery completeness gate still failed them closed with a 503 raised before the upstream was ever contacted, which the tools/list fan-out swallowed into HTTP 200 with an empty tool list. Any upstream that publishes no RFC 9728 metadata, including every OpenAPI-backed internal API, was permanently unusable. A failed discovery is now fatal only to servers whose OAuth flow the gateway runs itself. Discovery still runs for the forwarding modes, so /authorize, /token and /register keep resolving their endpoints, and each keeps its own 400 when they are missing. MCPServer.is_client_forwarded_token now owns the mode pair that five call sites spelled inline, one of which had already named it is_client_forwarded_mode.		2026-08-19 01:32:41 +00:00
..
mcp_server	fix(mcp): serve token-forwarding servers when oauth discovery fails (#37399)	2026-08-19 01:32:41 +00:00