MCP server name normalization and platform toolset fixes
NousResearch/hermes-agent · cluster 6901 · gateway
Data as of
Nothing open on GitHub. Fix merged in #7654. Check it covers your case.
The short answer
- Known?
- Yes. 8 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #7654. 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
- Nothing open on GitHub.
Multiple bugs and fixes related to numeric MCP server names causing TypeErrors and stale no_mcp entries persisting incorrectly in _save_platform_tools. One unrelated Discord toolset member is also present.
Open issues0
Open PRs0
Fixes on record
-
#7654 fix: final batch — MCP names, zombies, vision hardening, test isolation (Buckets S+T)
files:
agent/skill_commands.py,cron/scheduler.py,environments/tool_call_parsers/hermes_parser.py,environments/tool_call_parsers/mistral_parser.py,hermes_cli/tools_config.py,tests/gateway/test_approve_deny_commands.py,tests/hermes_cli/test_tools_config.py,tests/tools/test_approval.py,tests/tools/test_managed_media_gateways.py,tests/tools/test_vision_tools.py,tools/process_registry.py,tools/vision_tools.py
5 PRs closed without merging
From the close comments: done elsewhere 3 · merged via another change 2
-
#6962 fix: normalize numeric MCP server names to str (fixes #6901) · merged via another change →
#7654 -
#13086 fix(cli): clear stale no_mcp and normalize numeric toolset names on save (#13028) · done elsewhere →
9d7b64b,#13028 -
#14101 fix(cli): normalize saved platform tool entries · done elsewhere →
9d7b64b,#13086,#13028 -
#14149 fix(cli): clear stale no_mcp when saving platform toolsets · merged via another change →
9d7b64b,#13086 - #15091 fix(discord): end-to-end Discord support — toolset loading, tool split, and context injection · done elsewhere
Closed issues · 2
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.23: 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
- gateway
- Merged PRs
- #7654
- Closed issues
- 2
- Attempts
- 5 PRs closed without merging
- Fix link checked
- 11 Apr 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.