v0.2.1: publish to official MCP Registry - #9
Merged
Conversation
Submits recon-crypto-mcp to the official MCP Registry at registry.modelcontextprotocol.io. The registry feeds downstream directories (PulseMCP ingests it daily, Glama indexes from it, etc.) so this single submission covers most of the listing surface. Changes: - package.json: add `mcpName: io.github.szhygulin/recon-crypto-mcp` (registry validates that the published npm tarball's package.json contains this field matching the server.json name) and bump to 0.2.1 - server.json: registry manifest with stdio transport, optional env vars (RPC, Etherscan, 1inch, WalletConnect) - publish.yml: after npm publish, install mcp-publisher, authenticate via GitHub OIDC (no extra secret needed beyond existing id-token: write), and publish the server entry Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This was referenced Apr 27, 2026
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.
Summary
package.jsoncarries the newmcpNamefield that the MCP Registry validates againstserver.json.server.jsonat repo root — the registry manifest. Nameio.github.szhygulin/recon-crypto-mcp, stdio transport, optional env vars documented..github/workflows/publish.ymlwith three steps afternpm publish: installmcp-publisher,mcp-publisher login github-oidc,mcp-publisher publish. No new secret needed; the existingid-token: writepermission covers OIDC auth.Why bother: PulseMCP, Glama, and others ingest from the official registry, so this single submission cascades downstream.
Test plan
npm run buildcleannpm test— all passingworkflow_dispatchto publish v0.2.1 to npm + register on MCP Registrycurl https://registry.modelcontextprotocol.io/v0/servers?search=recon-crypto-mcp🤖 Generated with Claude Code