Developer tools Model Context Protocol
Official MCP Registry API
Browse the official registry’s public server records, including package metadata and remote connection addresses.
Source review: 2026-10-18 · Imported: 1 November 2026
A practical starting point
What could you build?
Build a searchable MCP catalogue that helps users find a server before reviewing its documentation.
Before you connect
Registry presence is discovery metadata, not a security endorsement. Check the publisher and permissions before connecting.
Capabilities & requirements
Dated specifications from the licensed source dataset. “Not published” indicates missing information, rather than confirmed absence.
| Capability | Details and source |
|---|---|
| Status | Preview Breaking changes or data resets may occur before general availability. Source (external) · Verified 2026-10-18 on https://modelcontextprotocol.io/registry/about |
| API key required | No key for reads GET /v0.1/servers returned HTTP 200 without credentials. Source (external) · Verified 2026-10-18 by test request to https://registry.modelcontextprotocol.io/v0.1/servers?search=gitlab&version=latest&limit=2 |
| Free tier | Free Reads are open; publishing needs namespace verification. Source (external) · Verified 2026-10-18 on https://raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/reference/api/official-registry-api.md |
| Rate limit | Not published No numeric limit published and no rate-limit headers seen; aggregators are asked to sync about hourly. Searches took up to ~19 s or timed out in the source publisher’s tests. Source (external) · Not published by vendor: checked 2026-10-18 on https://modelcontextprotocol.io/registry/about |
| Official MCP server | Not applicable It is a REST directory of MCP servers, not an MCP server itself. Source (external) · Verified 2026-10-18 on https://modelcontextprotocol.io/registry/about |
| Official SDK | OpenAPI spec + publisher CLI An OpenAPI spec is published; the CLI is for publishing, not reading. Source (external) · Verified 2026-10-18 on https://raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/reference/api/official-registry-api.md |
| Data license / terms | Metadata CC0 1.0 Submitted server metadata is dedicated to the public domain; registry code is Apache-2.0/MIT. Source (external) · Verified 2026-10-18 on https://modelcontextprotocol.io/registry/terms-of-service |
| Commercial use allowed | CC0 metadata Public-domain metadata; the terms cite a company pulling registry data as a permitted example. Source (external) · Verified 2026-10-18 on https://modelcontextprotocol.io/registry/terms-of-service |
| CORS / browser use | Access-Control-Allow-Origin: * Preflight returned 204 with *. Source (external) · Verified 2026-10-18 by test request to https://registry.modelcontextprotocol.io/v0.1/servers |
| Freshness / coverage | Live; updated_since for sync Publishers push updates; deleted entries show with include_deleted. Source (external) · Verified 2026-10-18 on https://raw.githubusercontent.com/modelcontextprotocol/registry/main/docs/reference/api/official-registry-api.md |
Operational reference
Additional facts and qualifications retained from AgentAPIList’s CC BY 4.0 dataset, with provider references.
API key / auth
None for reads: our GET /v0.1/servers requests on 2026-10-18 returned HTTP 200 with no credentials. Publishing needs GitHub OAuth or OIDC, or DNS or HTTP verification of your domain.
Provider reference (external)Rate limit
No numeric limit is published and our responses carried no rate-limit headers. The registry asks aggregators to sync about once an hour. Search was slow in the source publisher’s tests: one call took about 19 seconds and others timed out at 20–30 seconds.
Provider reference (external)Terms
Official MCP Registry Terms of Service (effective 2025-09-02): provided as is, users must be 18+, and submitted server metadata is dedicated to the public domain under CC0 1.0.
Provider reference (external)Status
Preview: the registry says breaking changes or data resets may occur before general availability. The live service reported version 1.8.1 on 2026-10-18.
Provider reference (external)Intended use
Meant mainly for downstream aggregators and marketplaces; the registry says host applications should use a downstream registry that implements the same OpenAPI spec. Security scanning is left to package registries and aggregators.
Provider reference (external)Setup references
HTTP request example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=gitlab&version=latest&limit=2"Agent connection example
Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.
// Minimal agent tool
{
"name": "find_mcp_server",
"description": "Search the official MCP Registry for public MCP servers by name.",
"input_schema": {
"type": "object",
"properties": { "q": { "type": "string", "description": "Substring of the server name, e.g. gitlab" } },
"required": ["q"]
}
}
// Implementation: GET https://registry.modelcontextprotocol.io/v0.1/servers?search={q}&version=latest&limit=10
// Allow 30 s timeouts; search can be slow.A tool schema needs an HTTP implementation; it does not by itself install an MCP server. Keep credentials out of browser code.
Other connections to explore
- Flow iMessage API (external)
- Smithery (external)
- PulseMCP (external)
- AgentAPIList MCP (external)
- Shop MCP (external)
Source & reuse
Download the complete licensed source snapshot (JSON), including the original source’s caveats, alternative notes and examples.