Track follow-up: GitHub MCP Registry onboarding visibility

[edithatogo]

Summary

The official MCP Registry lists io.github.edithatogo/fyi-mcp version 0.1.2 as active/latest, but GitHub's curated MCP Registry surface at https://github.com/mcp does not appear to list fyi-mcp yet.

GitHub discussion evidence indicates github.com/mcp can sync versions from the open-source/official registry only after a server has been manually onboarded. Initial onboarding remains a manual curation process.

Acceptance Criteria

• fyi-mcp is visible/searchable on https://github.com/mcp.
• The listing points to the current official MCP Registry server io.github.edithatogo/fyi-mcp.
• Published version is 0.1.2 or newer after GitHub onboarding/version sync.
• Any GitHub-side curation or submission requirement is captured with exact evidence.

Evidence

• Official MCP Registry API shows io.github.edithatogo/fyi-mcp version 0.1.2 as active/latest.
• GitHub MCP Registry search page for fyi-mcp did not show a matching server listing during the 2026-07-02 check.
• GitHub discussion github/github-mcp-server#1257 says the GitHub MCP Registry can sync versions from the open-source registry after onboarding, but new server onboarding is still manual curation.

Next Steps

1. Recheck https://github.com/mcp?q=fyi-mcp after the official registry has had more time to propagate.
2. If still absent, identify the supported GitHub support/community route for curated onboarding.
3. Keep the official MCP Registry, Smithery, and Glama tracking issues cross-referenced so registry status is reviewed as a set.

[edithatogo]

Verification 2026-07-09

Official MCP Registry (still good)

• io.github.edithatogo/fyi-mcp version 0.1.2 is active/latest
• API: https://registry.modelcontextprotocol.io/v0/servers?search=fyi-mcp

GitHub curated surface

• https://github.com/mcp?q=fyi-mcp still does not expose a usable public listing for fyi-mcp (page load/auth surface remains non-deterministic for bots; manual search also previously empty)
• Remains blocked on GitHub manual curation/onboarding after official-registry publication

No code change unblocks this; leave open with blocked-external.

[edithatogo]

Conductor track mapping

Track: external follow-up — related to registry-distribution-expansion (#45)

Status: Blocked-external

Evidence:

• Official MCP Registry: io.github.edithatogo/fyi-mcp v0.1.2 active (server.json)
• Documented in README registry table + matrix (PR chore: conductor closeout (code-scanning, upstream, registry) #127, docs: registries on README + coverage gate alignment #129)

Remaining: GitHub curated github.com/mcp onboarding is manual curation; no code change unblocks.

[edithatogo]

External follow-up action (2026-07-09)

Live recheck

• OSS registry: io.github.edithatogo/fyi-mcp 0.1.2 active + isLatest ✅
• github.com/mcp search / direct path: still no curated listing (404)

Onboarding request filed

Posted on GitHub discussion per curator guidance (manual onboarding after OSS publish):

github/github-mcp-server#1257 (comment)

Repo support (PR #133)

• Playbook: docs/external-registry-followups.md
• Matrix updated with evidence + discussion link

Leaving open until fyi-mcp appears on https://github.com/mcp (then verify version ≥ 0.1.2).

[edithatogo]

Unblock action 2026-07-09

Live recheck

• Official OSS registry: io.github.edithatogo/fyi-mcp 0.1.2 active + isLatest ✅
• https://github.com/mcp?q=fyi-mcp — page 200 but only echoes the search query; no curated server card (no edithatogo hits in HTML)
• Direct: github.com/mcp/io.github.edithatogo/fyi-mcp → 404

Onboarding requests (filed; no curator reply yet)

• Dedicated Q&A: Onboarding request: io.github.edithatogo/fyi-mcp for github.com/mcp github/github-mcp-server#2844
• Thread comment: MCP Server Published But Not Visible on github.com/mcp Registry github/github-mcp-server#1257 (comment)
• Pattern cross-link: Server visible in Official Registry API but not discoverable on github.com/mcp search modelcontextprotocol/registry#1107 (comment)

Repo (PR #134)

Playbook + matrix updated with request URLs.

No further code change unblocks curated listing — waiting on GitHub product/curation.