Official MCP Registry by Anthropic

Anthropic has now officially launched MCP Registry.

The registry will MCP servers to improve discoverability.

You can think of MCP as what npm is for JavaScript/Node projects.

Single source of truth for MCP servers

Until now, there are 100s of unofficial registries for MCP. (In fact, there is a registry for registry as well 😅)

We had to manually get ourselves added in most of them. And also those registory might not hold creditabolity as well.

But now with the official registry, we don’t have to worry about it. As long as we get our MCP added to the official registry, it will most probably be added to the unofficial registry (if they decide to use official registry data)

Instead of us getting ourselves registered in 100s of MCP registries, getting into the official registry would make our lives simple for us.

Getting Started

1. Adding your server

Prerequisites

• Make sure your MCP servers are published in a package registry like npm, PyPI, Docker Hub, etc

Install Publisher CLI

brew install mcp-publisher

Once you’ve installed the CLI, you need to init it in your MCP server package.

Initialise Your server.json file

You can do so by running

mcp-publisher init

It’ll create server.json with auto-detected values.

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json",
  "name": "io.github.yourname/your-server",
  "description": "A description of your MCP server",
  "version": "1.0.0",
  "packages": [
    {
      "registry_type": "npm",
      "identifier": "your-package-name",
      "version": "1.0.0"
    }
  ]
}

In the server.json file, there will be a name field which will act as a kind of like a namespace.

Right now, you can have either github or your own domain.

• io.github.yourname/* - Requires GitHub authentication
• com.yourcompany/* - Requires DNS or HTTP domain verification

Package Validation

Your package must also include the validation metadata to prove ownership.

For example, in case your MCP is a NPM package, you’ll need to add the mcpName in your package.json as mentioned in the server.json

Example:

{
  "name": "your-npm-package",
  "version": "1.0.0",
  "mcpName": "io.github.username/server-name"
}

You can learn more about authentication, publishing the package, security, etc here

2. Accessing MCP Server data

You can access the MCP server-related things in the following endpoints.

Base URL: https://registry.modelcontextprotocol.io/v0/servers

Server Endpoints

You can play around with their interactive API docs as well

You can use this information to build your own sub-registry with enhanced data.

Or you could be AI Coding tool which has a support for MCP tools and you want to provider a frictionless way for your users to install the MCP.

Reference

• Introducing the MCP Registry | mcp blog

Happy listing MCPs!