# NousResearch/hermes-agent · Add Magnific to MCP catalog

## Open now

- 1 issue, 1 PR open on GitHub.
- #88968: \[Feature\]: Add Magnific (mcp.magnific.com) to the MCP catalog
- PR #96961: feat(mcp): add Magnific to the MCP catalog

These issues and pull requests all concern adding Magnific (mcp.magnific.com) as an entry to the MCP catalog. The members appear to be duplicate or closely related submissions for the same feature request.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## 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 `0.67`: 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.

## Open related issues

- #88968: \[Feature\]: Add Magnific (mcp.magnific.com) to the MCP catalog

## Prior & competing PRs

- **#88969: feat(mcp): add Magnific to the MCP catalog**. closed without merge
  - maintainer direction: category `stale_abandoned`; implication `active`; refs `#96961`
- **#96961: feat(mcp): add Magnific to the MCP catalog**. open
  - maintainer direction: category `superseded_by_pr`; implication `superseded`
  - files: `contributors/emails/[redacted:email]`, `optional-mcps/magnific/manifest.yaml`

## Fix status

- No merged fix on record.
- Subsystem: `mcp`