The official MCP registry

The official MCP registry is a public metadata catalog run by the Model Context Protocol project. It stores a server.json for each server — name, description, version, repository, and how to run it (an npm, PyPI, Docker/OCI, NuGet or MCPB package, and/or a hosted remote URL) — but it does not host code. Directories and clients, including MCPSkillHub, read from it.

As of this page's last update, MCPSkillHub indexes 36,358 servers from the official registry, alongside servers from GitHub lists and npm.

What a server.json contains

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "name": "io.github.you/weather",
  "description": "Forecasts and alerts for any city.",
  "version": "1.2.0",
  "repository": { "url": "https://github.com/you/weather-mcp", "source": "github" },
  "packages": [{
    "registryType": "npm",
    "identifier": "@you/weather-mcp",
    "version": "1.2.0",
    "transport": { "type": "stdio" },
    "environmentVariables": [{ "name": "WEATHER_API_KEY", "isRequired": true, "isSecret": true }]
  }]
}

Namespaces

Names are reverse-DNS style. io.github.<user>/… names are verified by signing in with GitHub; names under your own domain (for example com.example/…) are verified with a DNS or HTTP challenge.

How to publish

# install the publisher CLI, then from your repo:
mcp-publisher init        # generates server.json
mcp-publisher login github
mcp-publisher publish

Your package must already be published to its own registry (npm, PyPI, etc.); the MCP registry only points to it.

Reading the API

GET https://registry.modelcontextprotocol.io/v0.1/servers?version=latest&limit=100
GET https://registry.modelcontextprotocol.io/v0.1/servers?version=latest&cursor=<nextCursor>

Pagination is cursor-based (metadata.nextCursor). Without version=latest every historical version is returned.

How MCPSkillHub relates to it

We are independent and not affiliated with the MCP project. We sync the registry weekly, merge it with servers from GitHub and npm, then add what the registry doesn't: install snippets for every client, and measured token cost, security signals and startup performance.