Model Context Protocol

MCP Registry API

Search the official MCP Registry, read server versions and install details, validate a server.json and publish your own server.

Developer toolsGuided#mcp#registry#server-json#ai-agents

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

The MCP Registry at https://registry.modelcontextprotocol.io is the official public catalogue of MCP servers, run by the Model Context Protocol project. It stores metadata only: each entry is a server.json that names the server, describes it, and says how to reach it, either remotes (a hosted Streamable HTTP or SSE URL plus any headers to send) or packages (an npm, PyPI, NuGet, OCI or MCPB package to run locally, with its arguments and environment variables). Marketplaces and client apps read it to build their own directories; server authors publish to it so their server can be found. The registry is in preview: shapes can change and data may be reset before general availability.

Credentials

  • Reading (folders 1-3) needs nothing: no account, no key.
  • Publishing needs a short-lived Registry JWT that proves you own the name's namespace:
  1. GitHub namespace io.github.<username>/*: create a GitHub Personal Access Token at https://github.com/settings/tokens (no repository scopes needed; add read:org to publish under an organization you own), put it in githubToken, run Exchange a GitHub token.
  2. Domain namespace like com.example/*: put a v=MCPv1; k=ed25519; p=... TXT record on your domain's apex, sign a timestamp, and exchange it (or use HTTP proof at /.well-known/mcp-registry-auth). The mcp-publisher CLI automates both; see https://modelcontextprotocol.io/registry/authentication
  3. The exchange saves registryToken, sent as Authorization: Bearer to publish or change status.

Base URL and versions

One environment: https://registry.modelcontextprotocol.io. This collection uses the /v0.1 paths that the current docs use; older /v0 paths are still served. Path parameters are URL-encoded, so io.github.upstash/context7 becomes io.github.upstash%2Fcontext7 in serverName.

Run order

  1. Browse: health, ping, version, search (version=latest), list with paging (cursor is saved for you) and updated_since.
  2. One server: latest, all versions, an exact version, including deleted ones, and a 404.
  3. Validate a server.json before publishing (no token).
  4. Publish: exchange a token, publish a version, change a version's status.

Limits

There is no published per-key quota, but the registry is meant to be read by aggregators on a schedule (roughly hourly), not per user request: cache results, use updated_since for incremental sync, request compressed responses, and back off on errors or rate limiting. limit is 1-100 per page. Publisher-provided _meta is capped at 4 KB.

Common errors

StatusMeaningWhat to do
404 Server not foundUnknown name or the slash was not encodedEncode / as %2F; check spelling with search
422 search must contain at least 3 charactersSearch term too shortUse 3+ characters
422 validation failedserver.json breaks the schemaRead errors[].location and message
422 header.Authorization missingPublish without a tokenExchange a token first
401 / 403Token expired or namespace not yoursLog in again; publish under your own namespace

Errors use RFC 9457 problem details (title, status, detail, errors).

Links

  • About the registry: https://modelcontextprotocol.io/registry/about
  • Quickstart (publishing): https://modelcontextprotocol.io/registry/quickstart
  • Consuming the API (aggregators): https://modelcontextprotocol.io/registry/registry-aggregators
  • Versioning rules: https://modelcontextprotocol.io/registry/versioning
  • Live API reference: https://registry.modelcontextprotocol.io/docs and OpenAPI at https://registry.modelcontextprotocol.io/openapi.yaml
  • Source: https://github.com/modelcontextprotocol/registry

Endpoints 18

1. Start here: browse servers

  • GETHealth/v0.1/healthChecks that the registry is up. Returns status: ok and the GitHub OAuth client id the publisher CLI uses for its device login, which is public information,…
  • GETPing/v0.1/pingThe smallest liveness probe: answers {"pong": true}. Use it in monitors instead of listing servers, which is heavier and counts against fair use.
  • GETRegistry version/v0.1/versionReturns the running registry build: application version, git_commit and build_time. Handy when a response shape changes during the preview period and you need…
  • GETSearch servers (latest versions)/v0.1/serversSearches server names by substring and returns only the newest version of each match (version=latest). search needs at least 3 characters or the API answers…
  • GETList all servers (first page)/v0.1/serversLists every server version, ordered by name and then version string (as text, not semver). Without version=latest you also get superseded versions. The test…
  • GETList all servers (next page)/v0.1/serversFetches the next page with the cursor saved by the previous request. Keep every other filter identical while paging; when nextCursor is missing you have…
  • GETServers updated since a timestamp/v0.1/serversReturns only servers changed after an RFC 3339 timestamp, for incremental sync. Deleted servers are included automatically here so you can remove them from…

2. One server and its versions

  • GETLatest version of a server/v0.1/servers/{{serverName}}/versions/latestFetches one server's newest published version using the special version latest. The body is a single entry (server + _meta); read remotes for a hosted URL and…
  • GETAll versions of a server/v0.1/servers/{{serverName}}/versionsLists every published version of one server with the same entry shape as the list endpoint and metadata.count. Version metadata is immutable once published,…
  • GETOne exact version/v0.1/servers/{{serverName}}/versions/{{serverVersion}}Fetches a specific version by its exact string (URL-encoded if it contains special characters). Useful when a client pinned a version and wants the exact…
  • GETInclude deleted versions/v0.1/servers/{{serverName}}/versionsAdds include_deleted=true so versions whose status is deleted are returned too. Deleted servers are hidden by default (often spam or policy removals) but…
  • GETUnknown server (404)/v0.1/servers/com.example%2Fdoes-not-exist/versions/latestShows the error format: the registry uses RFC 9457 problem details (title, status, detail, sometimes an errors list with location and message). An unknown or…

3. Check a server.json before publishing

  • POSTValidate a server.json/v0.1/validateValidates a complete server.json for a hosted server. Required fields are $schema, name (reverse-DNS namespace/name), description and version; add remotes for…
  • POSTValidate an invalid server.json/v0.1/validateSends a server.json with a bare name and a version range to show what rejection looks like: HTTP 422 problem details with an errors list naming each failing…

4. Publishing (needs a Registry token)

  • POSTExchange a GitHub token for a Registry JWT/v0.1/auth/github-atTrades a GitHub access token (a Personal Access Token works; classic PATs need read:org to publish under an organization) for a Registry JWT. The response has…
  • POSTExchange a DNS signature for a Registry JWT/v0.1/auth/dnsDomain-based login for names like com.example/*: publish a v=MCPv1; k=ed25519; p=<public key> TXT record on the apex of your domain, sign the current RFC 3339…
  • POSTPublish a server version/v0.1/publishPublishes the server.json in the body as a new version. Needs Authorization: Bearer <registry JWT> whose namespace matches name. Each version string can be…
  • PATCHDeprecate or delete a version (status)/v0.1/servers/com.example%2Fweather/versions/1.0.0/statusChanges only the lifecycle status of one version: active, deprecated or deleted, with an optional statusMessage up to 500 characters. Deleted versions…

API details

Base URL
https://registry.modelcontextprotocol.io
Authentication
A bearer token in the Authorization header
Operations
18 operations on 18 pathsGET 12POST 5PATCH 1
Main resources
1. Start here: browse servers 72. One server and its versions 53. Check a server.json before publishing 24. Publishing (needs a Registry token) 4
Description format
Swastik Codes guided collection, API version checked against the docs on 2026-11-18

How to test the MCP Registry API in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the MCP Registry API collection, without the publisher's secrets.
  3. Add your credentialsThis API uses A bearer token in the Authorization header. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “Health” (GET /v0.1/health), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the MCP Registry API?

Search the official MCP Registry, read server versions and install details, validate a server.json and publish your own server. It is listed under Developer tools and has 18 endpoints.

Who publishes the MCP Registry API?

It is listed from Model Context Protocol's public API description (an OpenAPI document), not published by Model Context Protocol on Swastik Codes. Anyone who controls modelcontextprotocol.io can claim the profile by adding a DNS TXT record.

What is the base URL of the MCP Registry API?

Requests go to https://registry.modelcontextprotocol.io. Endpoint paths are added to this base URL.

How do I authenticate with the MCP Registry API?

With A bearer token in the Authorization header.

How many endpoints does the MCP Registry API have?

18 operations on 18 paths (12 GET, 5 POST, 1 PATCH). The largest groups are 1. Start here: browse servers, 2. One server and its versions, 3. Check a server.json before publishing, 4. Publishing (needs a Registry token).

Is forking the MCP Registry API free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.