MCP probe timeout misclassified as auth failure
NousResearch/hermes-agent · cluster 119232 · apps/desktop
Data as of
3 open items. Fix attempted, not merged.
The short answer
1open issue
2open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug where MCP server probe timeouts are incorrectly reported as authentication failures, likely due to regex matching OAuth-related wording in error messages. Multiple fixes address classifying auth vs. timeout failures more accurately.
Open issues1
- Issue#119232[Bug]: Desktop MCP card reports "Needs authentication" for a no-auth server whenever the probe times out (auth regex matches Hermes' own "OAuth" wording)
Open PRs2
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#119337 fix(mcp): a 401 is an auth refusal, and a timeout is not one · superseded by another PR →
#119235,#119240
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- apps/desktop
- Closed issues
- 0
- Attempts
- 1 PR closed without merging