NousResearch/hermes-agent

MCP connection identity isolation for mTLS and OAuth

Cluster 109429. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #110193 on 13 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #110193. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #110193. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #110193 Pick up a Lab task

These issues and PRs address a bug where mTLS client certificates were excluded from MCP connection identity, causing authenticated connections to leak across multiplexed profiles. The work involves including mTLS credentials in connection identity and isolating mTLS and OAuth connections within their respective profile scopes.

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.

#110193 MCP connections authenticated by OAuth or mTLS are no longer adopted across multiplexed profiles (#109422, #109429; salvage #109428, #109434, #110021)

merged to main

files: tests/tools/test_mcp_multiplex_connection_keys.py, tools/mcp_tool_registration.py, website/docs/reference/mcp-config-reference.md, website/docs/user-guide/multi-profile-gateways.md

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

#109434 fix(mcp): include mTLS credentials in connection identity · done elsewhere → 630a4eb, #110193
#109437 fix(mcp): isolate mTLS connections across profile scopes (#109429) · duplicate → #109434

Closed issues · 1

Closed#109429mTLS client certs excluded from MCP connection identity - same cross-profile leak shape as #109422

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

Merged PRs: #110193
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 13 Sep 2026

For your agent

The same facts, typed.

cluster/109429.json
cluster/109429.md