Cairn
NousResearch/hermes-agent

MCP discovery ignoring managed-scope server config

Cluster 91073 · mcp. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 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 1 PR.

A bug where the MCP discovery probe only reads raw user config, missing servers declared in Managed Scope. Related fixes address making discovery honor the managed-scope configuration.

Open issues1

  • Issue#91073[Bug]: MCP discovery probe reads only the raw user config — mcp_servers declared in Managed Scope never starts discovery

Open PRs1

  • PR#91076fix(mcp): honor Managed Scope in the discovery gate

1 PR closed without merging

From the close comments: duplicate 1

  • #91102 fix(mcp): discovery probe honors managed-scope mcp_servers (#91073) · duplicate → #91076
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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/91073.json
cluster/91073.md