---
title: "Publishing to the official MCP Registry | Invokary"
description: "How to publish a remote MCP server to the official MCP Registry: server.json remotes, namespace authentication and what preview status means."
canonical: "https://invokary.com/platforms/mcp-registry"
dateModified: "2026-10-04"
---

# Publishing to the MCP Registry

## How do you publish an MCP server to the Official MCP Registry?

Describe the server in a server.json whose remotes property lists its public URL, then authenticate the namespace you publish under: GitHub for io.github.\* names, or DNS or HTTP for a domain you control. The registry is still in preview, so breaking changes or data resets may happen before general availability. Invokary tracks each rule with its source.

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](https://invokary.com/about) · Last verified: October 4, 2026

[Book a $750 Audit](https://invokary.com/book) · [How the Connector Launch Sprint works](https://invokary.com/services/connector-launch-sprint)

Invokary is an independent studio. We are not affiliated with or endorsed by Anthropic, OpenAI or Anysphere.

## Steps to get listed

In order, each step linked to the requirement it comes from.

1. [Make the server publicly accessible at its remote URL.](https://invokary.com/platforms/mcp-registry#mcp-registry.server-json)
2. [Write a server.json whose remotes property lists that URL.](https://invokary.com/platforms/mcp-registry#mcp-registry.server-json)
3. [Authenticate your namespace: GitHub for io.github.\* names, DNS or HTTP for a domain you control.](https://invokary.com/platforms/mcp-registry#mcp-registry.namespace)
4. [Publish, and keep an eye on the registry while it is in preview: breaking changes or data resets may happen.](https://invokary.com/platforms/mcp-registry#mcp-registry.preview)

The platform decides whether to list your connector or plugin and where it appears. We can't guarantee either.

### We went through this with our own server

We published our own MCP server to the registry on October 5, 2026, as com.invokary/platform-requirements. We authenticated the com.invokary namespace over HTTP, with a public key served at invokary.com/.well-known/mcp-registry-auth, then published its server.json with the registry's mcp-publisher tool.

[See our server and where it is listed](https://invokary.com/work)

## Requirements

Each requirement shows where it comes from and when we last checked it.

### Submission

- A remote server is published with a server.json whose remotes property lists its URL, and the server must be publicly accessible there.

  Official source · Source: [MCP Registry: Publishing remote servers](https://modelcontextprotocol.io/registry/remote-servers) · Checked October 4, 2026

  Permalink: <https://invokary.com/platforms/mcp-registry#mcp-registry.server-json>

### Who can submit

- You authenticate the namespace you publish under: GitHub for io.github.\* names, or DNS or HTTP for a domain you control.

  Official source · Source: [MCP Registry: How to authenticate when publishing](https://modelcontextprotocol.io/registry/authentication) · Checked October 4, 2026

  Permalink: <https://invokary.com/platforms/mcp-registry#mcp-registry.namespace>

### Limits

- The registry is in preview: breaking changes or data resets may happen before general availability.

  Official source · Source: [MCP Registry: Publishing remote servers](https://modelcontextprotocol.io/registry/remote-servers); [MCP Registry: How to authenticate when publishing](https://modelcontextprotocol.io/registry/authentication) · Checked October 4, 2026

  Permalink: <https://invokary.com/platforms/mcp-registry#mcp-registry.preview>

- [Compare the four platforms side by side](https://invokary.com/platforms)
- [Query these requirements from your AI agent](https://invokary.com/open-source#mcp-server)
- [The terms on this page, defined](https://invokary.com/glossary)

## Common rejection risks

Ways a submission can miss the requirements above. Each risk links to the requirement behind it.

- A namespace you cannot authenticate

  Requirement: [You authenticate the namespace you publish under: GitHub for io.github.\* names, or DNS or HTTP for a domain you control.](https://invokary.com/platforms/mcp-registry#mcp-registry.namespace)

- A server.json that does not list your remote endpoint

  Requirement: [A remote server is published with a server.json whose remotes property lists its URL, and the server must be publicly accessible there.](https://invokary.com/platforms/mcp-registry#mcp-registry.server-json)

Already rejected?

- [Fix it with the Connector Upgrade](https://invokary.com/services/connector-upgrade)
- [Answer a security review with the Connector Trust Pack](https://invokary.com/services/connector-trust-pack)
- [Why connector submissions get rejected on Claude, ChatGPT and Cursor](https://invokary.com/guides/why-connector-submissions-get-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.

[How the Connector Launch Sprint works](https://invokary.com/services/connector-launch-sprint)

- [MCP OAuth for SaaS connectors: Client ID Metadata Documents, the DCR fallback and API keys](https://invokary.com/guides/mcp-oauth-for-saas-connectors)
- [MCP connector security: prompt injection, tool poisoning and SSRF](https://invokary.com/guides/mcp-connector-security)
- [MCP server best practices: tools, descriptions, hints and errors that pass review](https://invokary.com/guides/mcp-server-best-practices)

## What changed

No changes logged for this platform yet.

[All platform changes](https://invokary.com/platform-changes)

## Find out where you stand in five days.

$750. Credited in full to your build.

[Book a $750 Audit](https://invokary.com/book)
