NousResearch/hermes-agent

MCP JSON error body message extraction fix

Cluster 47867 · mcp. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 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 2 PRs.

These members address a bug where MCP error responses with JSON bodies were being double-encoded, obscuring readable error messages. The work involves extracting human-readable messages from nested JSON error bodies.

Open issues1

  • Issue#47867MCP isError errors with nested JSON bodies are double-encoded, hiding actionable messages from the model

Open PRs2

  • PR#47871fix(mcp): extract readable message from nested JSON isError bodies
  • PR#47894fix(mcp): extract message from JSON error bodies to prevent double-encoding

1 PR closed without merging

From the close comments: duplicate 1

  • #47956 fix(mcp): extract readable message from JSON error bodies (#47867) · duplicate → #47871, #47867, #47894
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
1 PR closed without merging

For your agent

The same facts, typed.