Submit to Official MCP Registry
The official, community-run metadata registry for public MCP servers, backed by Anthropic, GitHub, Microsoft and PulseMCP. You publish a server.json from the command line, and marketplaces and other directories pull new entries from its API, so one entry here can surface in several places.
Official MCP Registry at a glance
- Pricing
- Free
- No fee mentioned anywhere in the publishing docs
- Link type
- Nofollow
- No link to your site: the registry has no per-server pages. The browse page https://registry.modelcontextprotocol.io/ draws cards from its API in the browser, and the repository and website links are only created when a visitor clicks a card open. The HTML the server sends and the page rendered in Chrome both had zero links to any server's repository or website (checked 2026-11-12) What a dofollow link is
- Review
- Automatic
- Link back required
- No
- Account required
- No
- Domain Rating
- DR91
- Domain Rating by Ahrefs, checked Nov 11, 2026. A score of the whole site’s backlinks, not a Google metric.
- Tranco rank
- Not ranked
- No Tranco rank on record for this site.
- Who browses it
- MCP marketplaces, client apps and aggregators that sync server metadata, plus developers browsing the raw list
- Last checked
How to submit to Official MCP Registry
Open the Official MCP Registry submission page
This is the page makers use to add a product.
Have your assets ready
Name, tagline, description, logo and screenshots. The checklist below covers what to prepare so you can fill the form in one go.
Fill in the form carefully
Pick the most specific category the form offers and write the description for the people who browse Official MCP Registry (MCP marketplaces, client apps and aggregators that sync server metadata, plus developers browsing the raw list), not for search engines.
Check your listing
Listings go live without review. Open yours, check the details and check the link points to the right page.
Tips for Official MCP Registry
- There is no web form: install the mcp-publisher CLI, then run init, login and publish from your project folder.
- The server name decides the proof you need: io.github.<user>/... means a GitHub login, com.yourdomain/... means a DNS TXT record on the domain apex.
- Put a package-based server on npm, PyPI or another public registry first and add the mcpName field; keep the description under 100 characters or validation fails.
- Publish here first: mcp.directory and API Tracker both pull entries from this registry, and PulseMCP's submit page points makers here while it's paused.
From Official MCP Registry’s own guidelines and pages, in our words.
What to prepare
The basics every directory asks for, plus what matters most for developer tool directories.
- Product name and a one-line tagline (about 60 characters)
- A short description (1–2 sentences) and a longer one (a short paragraph)
- Square logo, at least 256×256 px, PNG or SVG
- 2–3 screenshots at a consistent size
- The exact page you want the link to point to
- Pricing model (free, freemium or paid) and a contact email
- Links to your docs and a quick-start or install command
- Your GitHub or GitLab repo, if public
- Supported languages, frameworks and platforms
- Pricing for the API or hosted tier, including free limits
Is Official MCP Registry worth it?
Good for discovery, not link equity
Links from Official MCP Registry listings carry rel="nofollow", so they pass little or no ranking value. Submit if its audience matches yours: the value is visitors and being findable where people browse.
- Domain Rating by Ahrefs: 91 (top tier). That's the strength of links to the whole site, not a promise about what your listing passes on.
- No Tranco rank on record, so we can’t say how much traffic it gets.
- Listings are published without human review.
- Free to list, so the only cost is your time.
This verdict is worked out from the facts above with fixed rules (link type, review, price, Domain Rating by Ahrefs, Tranco rank), not paid for. The directory has no say in it.
Questions about Official MCP Registry
Is Official MCP Registry free?
Yes. Listing on Official MCP Registry is free. Pricing details: No fee mentioned anywhere in the publishing docs. We checked on Nov 12, 2026.
Does Official MCP Registry give a dofollow link?
No. Listing links on Official MCP Registry are nofollow, so they pass little ranking value. They can still send visitors. Evidence: No link to your site: the registry has no per-server pages. The browse page https://registry.modelcontextprotocol.io/ draws cards from its API in the browser, and the repository and website links are only created when a visitor clicks a card open. The HTML the server sends and the page rendered in Chrome both had zero links to any server's repository or website (checked 2026-11-12).
How do I submit to Official MCP Registry?
Submit at https://modelcontextprotocol.io/registry/quickstart. Listings go live without human review. Tip: There is no web form: install the mcp-publisher CLI, then run init, login and publish from your project folder.
Alternatives to Official MCP Registry
All developer tool directoriesFree · Tranco #29
Free · Tranco #547
Free · DR 91 · Tranco #3,788
Free + paid options · DR 83 · Tranco #21,171
Free · DR 57 · Tranco #102,398
Free · DR 80 · Tranco #103,090
Also in these lists
Official MCP Registry appears on these niche lists, next to other places to submit the same kind of product.
All niche listsSources
The pages we opened on Nov 12, 2026 to write this page.
- registry.modelcontextprotocol.io/
- registry.modelcontextprotocol.io/v0.1/servers?limit=2
- modelcontextprotocol.io/registry/quickstart
- raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/modelcontextprotocol-io/quickstart.mdx
- raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/modelcontextprotocol-io/authentication.mdx
- raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/modelcontextprotocol-io/about.mdx
- raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/modelcontextprotocol-io/moderation-policy.mdx
- raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/modelcontextprotocol-io/faq.mdx