{"repo":"NousResearch/hermes-agent","public_id":"89412","display_label":"MCP OAuth not triggering for servers without authentication challenge","summary":"These members concern MCP OAuth handling when a server does not challenge unauthenticated requests, such as Google's Gmail MCP, including forcing the OAuth flow after a 200 response to initialize. One member also mentions honouring a configured oauth.scope and accepting Google's root-slash issuer, which are adjacent OAuth details.","subsystem":"mcp","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":1,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":89412,"title":"MCP OAuth flow never triggers for servers that don't challenge unauthenticated requests (e.g. Google's Gmail MCP)","url":null,"state":"open"},{"kind":"pr","number":53873,"title":"fix(mcp): force OAuth flow when server returns 200 for initialize without auth (#53870)","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#97010","number":97010},{"kind":"pr","value":"#53870","number":53870}],"category":"superseded_by_pr","implication":"superseded"},"merged":false},{"kind":"pr","number":144307,"title":"fix(mcp): honour configured oauth.scope, accept Google's root-slash issuer, let login authorize anonymous servers","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}