# NousResearch/hermes-agent · MCP OAuth device flow issuer selection fix

## Open now

- Nothing open on GitHub.

These items address a bug where the MCP OAuth device-code flow incorrectly selects an authorization server, specifically failing to match the issuer-bound server rather than defaulting to the first advertised one. The work involves fixing server selection logic to try valid device authorization servers.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #112195. Verify it addresses your case.
- **Recommended:** read PR #112195 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `1.00`: the share of member 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.

## Closed / duplicate issues

- #112060: \[Bug\]: Higgsfield MCP OAuth issuer mismatch; device-code flow cannot be selected

## Prior & competing PRs

- **#112195: fix(mcp): OAuth device login picks the issuer-bound authorization server instead of the first advertised one (#112060, #82416, salvage #112068)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `evals/mcp_device_flow.py`, `tests/tools/test_mcp_device_flow.py`, `tools/mcp_oauth_device.py`, `website/docs/reference/mcp-config-reference.md`
- **#112068: fix(mcp): try valid device authorization servers**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `551fe883d9`, `#112195`

## Fix status

- Merged to main in PR #112195 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-16`.