How to use the newly launched MCP Registry

 

The newly launched Model Context Protocol (MCP) Registry in preview is as an open catalog for publicly available MCP servers. This is key in providing discoverability of MCP servers and standardization of this process. The Registry serves as a source of truth for MCP Servers and has also published a process for adding MCP servers. The MCP Registry also allows to register public and private sub-registries. This is an interesting addition and bears some semblance to DNS in its design. The public sub-registry can be likened to a MCP marketplace for servers while a private sub-registry would be suitable for enterprises with stricter privacy and security requirements.

 

MCP Registry tracks MCP Servers

 

Accessing Data   

The Registry data can be accessed through the API provided. No authentication is required for read only access.

The base URL is https://registry.modelcontextprotocol.io

• GET /v0/servers - List all servers with pagination
• GET /v0/servers/{id} - Get full server details including packages and configuration

 

For instance, the following curl query can be used to get the list of servers

curl --request GET \ --url https://registry.modelcontextprotocol.io/v0/servers \ --header 'Accept: application/json, application/problem+json'

The details on usage is in the github link here

 

Publishing Servers 

This requires authentication and the client package to be installed

After installing the mcp-publisher client, the server.json file has be populated with the MCP server details to be added. Authentication can be done using github or DNS verification.  The last step is to publish the server.

The github link here has the complete set of steps for adding servers.

 

 

More details can be found in the link here.