Publishing to the MCP Registry
You publish a remote MCP server to the official MCP Registry with a server.json whose remotes list its public endpoint, under a namespace you authenticate: GitHub for io.github.* names, or DNS or HTTP for your own domain. The registry is in preview, so breaking changes or data resets can still happen.
Below is each requirement we track, with its source and the date we last checked it.
Reviewed by Mohd. Ashhar · Last verified:
Invokary is an independent studio. We are not affiliated with or endorsed by Anthropic, OpenAI or Anysphere.
Requirements
Submission
A remote server is published with a server.json whose remotes property lists its URL, and the server must be publicly accessible there.
Who can submit
You authenticate the namespace you publish under: GitHub for io.github.* names, or DNS or HTTP for a domain you control.
Limits
The registry is in preview: breaking changes or data resets may happen before general availability.
Official sourceSource: MCP Registry: Publishing remote servers; MCP Registry: How to authenticate when publishingChecked
Common rejection risks
A namespace you cannot authenticate
A server.json that does not list your remote endpoint
Already rejected?
How we handle it
- Every Launch Sprint includes the Registry server.json, whichever platforms you choose.
- The Audit maps where you and your competitors are listed across the Registry, Claude, ChatGPT and Cursor.
What changed
No changes logged for this platform yet.
All platform changes