Cairn
NousResearch/hermes-agent

MCP discovery failures from empty cacheScope values

Cluster 94992 · mcp. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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.

These issues and pull requests address MCP server discovery failures caused by empty or unexpected cacheScope values, including fixes to treat empty cacheScope as omitted and SDK upgrades for related compatibility.

Open issues1

  • Issue#94992MCP discovery fails when a server returns an empty cacheScope

Open PRs1

  • PR#94995fix(mcp): tolerate empty list cache scope

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #95145 fix(mcp): treat empty cacheScope as omitted to prevent discovery failure (#94992) · duplicate → #94995
  • #105438 fix(mcp): upgrade SDK for cross-revision responses · other
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.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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/94992.json
cluster/94992.md