MCP Registry

MCPDirectoryLevel: Intermediate
Logo MCP Registry

MCP Registry

3.5/5OPCAIOS rating

The official directory for finding servers; still new.

The official directory for finding and publishing MCP servers.

What is MCP Registry and who is it for?

The OPCAIOS tools library files MCP Registry under MCP: it is an MCP server. Short label: Directory. The official directory for finding and publishing MCP servers. The MCP Registry is the official directory of MCP servers, developed publicly by the community. The repository describes it as something like an app store for MCP servers, where AI applications and users find servers to connect to. Best suited to: IT teams looking for servers; developers who want to publish servers. According to OPCAIOS, the editorial score of MCP Registry is 3.5 out of 5: the official directory for finding servers; still new.

  • Platform: Web, API; mcp-publisher tool for macOS, Linux, Windows.
  • Difficulty to get started: intermediate.

Is MCP Registry free, and what does it cost?

According to OPCAIOS, the cost of MCP Registry is as follows. See the terms on the official page. Additionally, prices are set by the provider and can change, so compare with the official MCP Registry site before you pay. To compare costs, the MCP group of the library also includes Model Context Protocol (free), MCP Servers (free), and MCP specification (free).

What are the main features of MCP Registry?

According to OPCAIOS, the standout strengths of MCP Registry are official directory, metadata only, and name ownership verification, among others. Additionally, the list below explains each of the 6 recorded features.

  1. Official directory: The site has a search box, a list of recently updated servers and an option to show only the latest versions.
  2. Metadata only: The Registry does not hold source code or install packages, only points to packages published elsewhere.
  3. Name ownership verification: Names of the form io.github.username require GitHub login; custom domains need verification via DNS or HTTP.
  4. Supports many package types: npm, PyPI, NuGet, OCI and MCPB, plus remote servers via Streamable HTTP.
  5. Public API: An API Reference page is available for applications that want to read the server list automatically.
  6. Still in preview: Major changes may occur before it reaches general availability.

When should you use MCP Registry?

MCP Registry is used for 4 kinds of work. When using MCP Registry, the most typical case is finding servers for tools you use. Additionally, the main audience is IT teams looking for servers; developers who want to publish servers.

  1. Finding servers for tools you use: IT teams check whether the business software they use already has an official MCP server.
  2. Publishing the company's server: A software company publishes its MCP server so customers can find and connect to it easily.
  3. Checking a server's origin: See whether the server links to a code repository and a verified domain before installing.
  4. Building an internal catalogue: An internal app reads the Registry API to suggest suitable servers to staff.

How do you get started with MCP Registry?

When using MCP Registry for the first time, you go through 5 steps, which OPCAIOS rates as intermediate difficulty. The first step is to look up servers, and the last is to publish. The steps are listed in order below.

  1. Look up servers. Go to the Registry page, type a keyword and turn on showing only the latest versions.
  2. Install the publishing tool. If you want to publish your own server, install mcp-publisher (on macOS, with Homebrew).
  3. Create the server.json file. Run it in the server project folder to generate the metadata template, then fill in the description, repository and package.
  4. Sign in to GitHub. Authenticate via GitHub device login to prove your right to the name io.github.your-name.
  5. Publish. Once the package is on npm or PyPI and mcpName is declared, push the metadata to the Registry.

What is MCP Registry?

The MCP Registry is the official directory of MCP servers, developed publicly by the community. The repository describes it as something like an app store for MCP servers, where AI applications and users find servers to connect to.

The Registry stores only metadata (descriptive information), not the software packages themselves. The package must first be published on npm, PyPI, NuGet, OCI or MCPB, then the author uses the mcp-publisher tool to submit a server.json file to the Registry. Remote servers can also be registered by URL.

According to the repository, the Registry launched in preview on 08/09/2025 and data may still change or be deleted; the v0.1 API is feature-frozen, and a general availability (GA) release is being planned.

How much does MCP Registry cost?

See the terms on the official page

Prices are set by the provider and can change; check the official site for the latest.

Key features of MCP Registry

01

Official directory

The site has a search box, a list of recently updated servers and an option to show only the latest versions.

02

Metadata only

The Registry does not hold source code or install packages, only points to packages published elsewhere.

03

Name ownership verification

Names of the form io.github.username require GitHub login; custom domains need verification via DNS or HTTP.

04

Supports many package types

npm, PyPI, NuGet, OCI and MCPB, plus remote servers via Streamable HTTP.

05

Public API

An API Reference page is available for applications that want to read the server list automatically.

06

Still in preview

Major changes may occur before it reaches general availability.

What is MCP Registry used for?

Finding servers for tools you use

IT teams check whether the business software they use already has an official MCP server.

Publishing the company's server

A software company publishes its MCP server so customers can find and connect to it easily.

Checking a server's origin

See whether the server links to a code repository and a verified domain before installing.

Building an internal catalogue

An internal app reads the Registry API to suggest suitable servers to staff.

How to use MCP Registry

  1. 1

    Look up servers

    Go to the Registry page, type a keyword and turn on showing only the latest versions.

  2. 2

    Install the publishing tool

    If you want to publish your own server, install mcp-publisher (on macOS, with Homebrew).

    $brew install mcp-publisher
  3. 3

    Create the server.json file

    Run it in the server project folder to generate the metadata template, then fill in the description, repository and package.

    $mcp-publisher init
  4. 4

    Sign in to GitHub

    Authenticate via GitHub device login to prove your right to the name io.github.your-name.

    $mcp-publisher login github
  5. 5

    Publish

    Once the package is on npm or PyPI and mcpName is declared, push the metadata to the Registry.

    $mcp-publisher publish

MCP Registry video guides

MCP Registry Briefing: Standardizing MCP Servers & What It Means for Developers

Agentic AI Foundation

[Session] MCP Registry: The Path To (De-)Centralizing Discovery

Agentic AI Foundation

GitHub MCP Registry integrated in VS Code Insiders

Visual Studio Code

Real-world example: MCP Registry

Illustrative scenario

An accounting software startup in Can Tho wrote an MCP server that lets AI assistants look up ledgers. They publish the package to npm, add the mcpName field to package.json, then use mcp-publisher to submit the server to the Registry. Customers using AI apps can find the server by name and check the repository link before connecting.

Tips for using MCP Registry

  • Publish the package first

    The Registry stores only metadata, so the package must be on npm, PyPI and so on before running publish.

  • Validate before publishing

    Use mcp-publisher's validate command to check server.json without publishing.

  • Keep the description short

    The description field in server.json is limited to 100 characters.

  • Do not rely on it absolutely during preview

    The Registry may still change or reset data, so keep your own records.

MCP Registry: frequently asked questions

Does the Registry store server source code?

No, it stores only metadata and points to the server's package or URL.

Is a server on the Registry absolutely safe?

No such claim is made; the Registry verifies name ownership, and you still need to assess the code and access permissions yourself.

Can I use my company domain as the server name?

Yes, if you prove ownership of the domain via DNS or HTTP.

Is the Registry stable yet?

It is in preview; the v0.1 API has frozen major changes and a GA release is being planned.

Useful links

Want to apply this in your business?

OPCAIOS looks at your workflows, picks the right tools and sets them up with your team. The first call is free.

Book a call