NousResearch/hermes-agent

W3C trace-context propagation for outbound MCP calls

Cluster 52211 · 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, 1 issue 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.

These issues and PRs concern adding opt-in W3C trace-context (traceparent) header propagation to outbound MCP HTTP calls for distributed tracing support. The work spans a feature request, a bug/gap report, and related implementation efforts.

Open issues1

  • Issue#60177No OTel SDK / W3C trace-context propagation on outbound MCP HTTP calls

Open PRs1

  • PR#60466feat(telemetry): propagate W3C trace-context on outbound MCP HTTP calls (#60177)

1 PR closed without merging

From the close comments: done elsewhere 1

  • #78965 feat(mcp): opt-in W3C trace-context propagation for MCP tool calls · done elsewhere
Closed issues · 1
  • Closed#52211Feature: Propagate W3C traceparent headers to MCP servers for distributed tracing
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.39: 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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.