NousResearch/hermes-agent

MCP OAuth discovery and error reporting fixes

Cluster 113771. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #114902 on 18 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #114902. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #114902. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #114902, then check it covers your case.

Read #114902 Pick up a Lab task

These items address misleading error messages during MCP OAuth authorization-server discovery and fix issues where discovery failures, WAF-protected endpoints, and slow consent flows could produce confusing errors or port collisions on the callback.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#114902 fix(mcp): OAuth login discovers the advertised endpoints behind a WAF and a slow consent no longer collides on the callback port (#113771, salvage #103640, #93095)

merged to main

files: contributors/emails/[redacted:email], hermes_cli/mcp_config.py, tests/hermes_cli/test_mcp_config.py, tests/tools/test_mcp_oauth.py, tests/tools/test_mcp_oauth_cold_load_expiry.py, tests/tools/test_mcp_oauth_discovery_requests.py, tools/mcp_oauth.py, tools/mcp_oauth_manager.py, tools/mcp_oauth_provider.py, website/docs/reference/mcp-config-reference.md

1 PR closed without merging

From the close comments: superseded by another PR 1

#113775 fix(mcp): lead registration-failure errors with discovery context · superseded by another PR → 5a64a88, #114902, #113771, #103640, #93095

Closed issues · 1

Closed#113771MCP OAuth: failed authorization-server discovery is reported as "Registration failed: 404", hiding the real 403

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs: #114902
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 18 Sep 2026

For your agent

The same facts, typed.

cluster/113771.json
cluster/113771.md