NousResearch/hermes-agent

MCP OAuth flow timeout and port collision fixes

Cluster 103633 · mcp. Data as of 2026-10-26 12:29 UTC

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

open issue

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 0 issues 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 unresolved. That is separate from the fix event.
Still open: 1 issue and 0 PRs.

Next step: read #114902, then check whether your report is the one still open.

Read #114902 Pick up a Lab task

These items address issues in the MCP OAuth code-to-token exchange, including incomplete flows for servers mounted at a /mcp path, crashes caused by callback port reuse, and propagation of an extended connect timeout for OAuth probes. The work targets endpoint discovery behind WAFs and slow consent screens.

Open issues1

Issue#103633MCP OAuth: code→token exchange never completes for server with /mcp path (traveler.md); auto-retry crashes on 'callback port already in use'

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: merged via another change 1

#103640 fix(mcp): propagate an extended connect_timeout into config for OAuth probes · merged via another change → 5a64a88, #114902, #113771, #103640, #93095

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

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

For your agent

The same facts, typed.

cluster/103633.json
cluster/103633.md