NousResearch/hermes-agent
MCP server duplicate spawn and eager start issue
Cluster 58862 · mcp. Data as of
Nothing open on GitHub. Fix merged in #75915 on 1 Aug 2026. Check it covers your case.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #75915. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #75915. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a regression where MCP servers start all instances at boot, and related fixes to prevent duplicate spawns and stale connecting entries. The fixes add guards to skip servers already in a connecting state.
Open issues0
Open PRs0
Fixes on record
-
#75915 fix(mcp): guard against duplicate spawns and stale connecting entries (#58862)
files:
tests/tools/test_mcp_tool.py,tools/mcp_tool.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#58862[Regression] MCP servers eagerly start all instances at boot (config_version 33)
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
- mcp
- Merged PRs
- #75915
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 1 Aug 2026