server.json: 1.0.1 — repository link + icons for the GitHub MCP Registry - #2
Open
TaltonFiggins wants to merge 1 commit into
Open
server.json: 1.0.1 — repository link + icons for the GitHub MCP Registry#2TaltonFiggins wants to merge 1 commit into
TaltonFiggins wants to merge 1 commit into
Conversation
The published registry record (dev.modem/modem 1.0.0) predates the repository field in this file, and registry versions are immutable, so the link and icons only reach the registry via a version bump. Why it matters: github.com/mcp renders each listing as a repo-backed card (stars, language, license, topics, OG image). Entries with no repository have nothing to render — com.stripe/mcp resolves to stripe/agent-toolkit, com.figma.mcp/mcp to figma/mcp-server-guide. Icons point at raw.githubusercontent on main, so merge #1 first.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prep for the github.com/mcp listing. Depends on #1 — merge that first, the icon URLs point at
assets/onmain.What and why
The live registry record is
dev.modem/modem1.0.0, published 2026-09-02, and it has norepository— this file gained the field after that publish. Registry versions are immutable, so the only way to get the link (and the corrected description) into the registry is a version bump.This matters because github.com/mcp renders every listing as a repo-backed card — stars, primary language, license, topics, OG image all come from a GitHub repo:
com.stripe/mcpstripe/agent-toolkitcom.figma.mcp/mcpfigma/mcp-server-guidedev.modem/modem(today)Changes
version→1.0.1icons→ the three square exports from assets: export the square logo (SVG, 64px, 400px) #1 (400px PNG, 64px PNG, scalable SVG), per theIcondefinition in the 2025-12-11 schemaDescription is unchanged at 96 chars (schema cap is 100). Publishing 1.0.1 also replaces the stale description on the live record.
After merge
The apex TXT on
modem.devis already in place (v=MCPv1; k=ed25519; p=+x0+SSt5…), so publishing needs the matching private key from whoever ran the first publish.Not in this PR
server.jsonsays 1.0.1 while the running server reports0.1.0(DEV-3880). Orthogonal to this change, but a reviewer can see both.