NousResearch/hermes-agent

Lazy MCP servers wrongly shown as errors or misconfigured

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

Nothing open on GitHub. Fix merged in #112324 on 16 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 #112324. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #112324. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #112324 Pick up a Lab task

Lazy MCP servers were being reported with incorrect status — appearing as 'configured' or 'failed' with red banners and spurious warnings — despite their tools functioning correctly. These changes correct the status reporting to accurately reflect the lazy registration state.

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.

#112324 fix(mcp): lazy MCP servers show as lazy (not failed) in status, banner and startup discovery (#111717, slim redo of #100648)

merged to main

files: apps/shared/src/gateway-contract.generated.ts, apps/shared/src/gateway-contract.openrpc.json, cli-config.yaml.example, hermes_cli/banner.py, hermes_cli/mcp_startup.py, tests/hermes_cli/test_mcp_startup.py, tests/tools/test_mcp_lazy_start.py, tools/mcp_tool_discovery.py, tui_gateway/contracts/tools_mcp_plugins.py, ui-tui/src/components/branding.tsx, ui-tui/src/types.ts, website/docs/reference/mcp-config-reference.md, website/docs/user-guide/features/mcp.md

1 PR closed without merging

From the close comments: merged via another change 1

#100648 fix(mcp): report lazily registered servers as lazy, not configured or failed · merged via another change → fff1048, #112324

Closed issues · 1

Closed#111717[Bug]: lazy MCP servers are reported as "configured"/failed — red banner, "zero connected servers" warning and a discovery retry on every startup while their tools are registered and working

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: #112324
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/111717.json
cluster/111717.md