Launch platforms
How to submit to Official MCP Registry: cost, link and review time
The Official MCP Registry is free and has no web form: you publish a package to npm or another package registry, then run the mcp-publisher CLI to submit a server.json. There is no review queue, and the moderation policy says to expect minimal to no moderation. It serves metadata through an API and a basic browse page that links to repository and website URLs through script, so it gives no usable backlink. It is still labelled preview.
Last updated November 2026
Official MCP Registry at a glance
Every value below was read on 2026-11-01 from Official MCP Registry’s own pages or from the HTML of a live listing; a dash means we could not verify it.
| Submit page | modelcontextprotocol.io/registry/quickstart |
|---|---|
| Format | registry |
| Free option | Yes: publishing has no fee; the quickstart lists no payment step. |
| Paid options | None published |
| Website link | No outbound website linkThe registry serves JSON at /v0/servers and a landing page that builds server links with JavaScript; the server HTML contains no per-server listing link, so there is no rel to read. |
| Review time | No review queue is described; the quickstart shows publishing completing in the CLI. |
| Requirements | Package published to a package registry such as npm (the registry hosts metadata only); mcpName field in package.json matching the name in server.json; Authentication: GitHub for an io.github.<user>/ namespace, or DNS for a custom domain; mcp-publisher CLI installed |
| Best for | any server that ships as an npm, PyPI, NuGet or Docker package |
How to submit to Official MCP Registry
- Add an mcpName property to package.json, starting with io.github.<username>/ if you will use GitHub authentication.
- Publish the package itself to npm (or the matching registry), because the MCP Registry hosts metadata only.
- Install the mcp-publisher CLI with the release binary or Homebrew.
- Run mcp-publisher init to generate server.json, then edit the version and package details; its name must match mcpName.
- Authenticate with mcp-publisher login github (or use DNS authentication for your own domain).
- Run mcp-publisher publish, then confirm with a search on the registry API.
Is the Official MCP Registry worth it?
Yes for any server that is distributed as a package, because publishing is free and the other directories can ingest from it. The cost is some setup: a package on npm or similar, a manifest field and one CLI login. Do not expect traffic or links from it. The registry exposes data through an API and a simple browse page; the docs describe it as metadata that clients and sub-registries consume.
What to prepare before you publish to the Official MCP Registry
Prepare a published package with the mcpName property set, a repository URL, a version and transport details. For remote servers, the docs have a separate remote-servers page. If you want your own domain as the namespace instead of io.github.<user>, plan for DNS-based authentication. Keep names consistent: the name in server.json must match mcpName, and with GitHub authentication the name must start with io.github. followed by your username, or publishing is refused with a permission error.
Official MCP Registry trade-offs
The registry is labelled preview, and the docs warn that breaking changes or data resets may occur before general availability. Its moderation policy says it removes only illegal content, malware, spam and non-functioning servers, and that consumers should assume minimal to no moderation. It will not remove low-quality, buggy or duplicate servers, so a listing here is not an endorsement and not a differentiator.
How downstream directories use the registry
The registry's own moderation page says it relies on downstream subregistries to do deeper moderation, and that subregistries may have their own policies. That makes publishing here a distribution step: other directories and clients can read your server metadata from the API, so one publish can reach several places. It does not replace listing on human-facing directories. The API lists each server with status fields such as active and timestamps for when it was published and updated, which you can check with a plain GET request. Keep your version numbers current whenever you release, so consumers see the latest entry.
How we checked
We read Official MCP Registry’s own submission, pricing and policy pages on 2026-11-01, and for the link attribute we read the raw HTML of a live public listing rather than relying on the platform’s description. Listing checked: registry.modelcontextprotocol.io/. Prices and rules change; the date at the top is the last time each fact on this page was checked. Sources:
- publishing steps, requirements, preview notice (read 2026-11-01)
- moderation policy (read 2026-11-01)
- registry landing page HTML (read 2026-11-01)
- API response (JSON) (read 2026-11-01)
Toolfound publishes this page and runs its own launch board, so we are not neutral about launching. No platform paid to be profiled here. The rules we apply to ourselves are on the methodology page.
Common questions
Is the Official MCP Registry backlink dofollow?
There is no listing page link to rate. The registry serves JSON through its API, and its landing page builds server links in client-side script, so the server HTML contains no per-server link. Treat it as providing no backlink.
How much does it cost to publish to the Official MCP Registry?
The quickstart lists no fee. You need free npm and GitHub accounts, or a domain for DNS authentication.
How long does it take to be listed?
No review wait is described. The quickstart shows the CLI reporting a successful publish, after which the server appears in API search results.
What do I need to publish?
A published package with an mcpName property, a server.json whose name matches it, the mcp-publisher CLI, and GitHub or DNS authentication.
Is the registry still in preview?
Yes. The quickstart and moderation pages both state that it is currently in preview and that breaking changes or data resets may occur.
Other launch platforms we checked
- AlternativeTo: no outbound website link, free option
- AppSumo: dofollow (followed link), free option
- BetaList: dofollow (followed link), paid only
- DevHunt: conditional, free option
- Fazier: conditional, free option
- Futurepedia: dofollow (followed link), paid only
- Glama MCP directory: nofollow, free option
- Hacker News (Show HN): conditional, free option
- Launching Next: nofollow, free option
- mcp.so: conditional, free option
- Microlaunch: conditional, free option
- Peerlist: conditional, free option
- Reddit r/SideProject: no (rel="ugc"), free option
- SaaSHub: conditional, free option
- There's An AI For That: not verified, paid only
- Uneed: conditional, free option
Compare Official MCP Registry with every other platform in the launch guide, see which ones give a followed link in the dofollow directories guide, or browse all launch platform profiles. Toolfound also gives every product a free launch date and a permanent dofollow listing: submit a product.