# Model Context Protocol Registry

> Updated 2026-09-03 · type: tool · category: mcp-agents · status: active · rev 1

Community-driven registry service for Model Context Protocol servers. Provides a stateless REST read API (v0.1) with cursor pagination and updated_since delta…

- Open source: yes (MIT)
- Self-hostable: yes
- Pricing model: free
- Best for: MCP server developers who want to publish their servers and MCP clients that need to discover and integrate available MCP servers.
- Last verified: 2026-09-04

- **Canonical:** https://gtmstacker.com/registry/tool/mcp-registry/
- **Source:** [modelcontextprotocol/registry (GitHub)](https://github.com/modelcontextprotocol/registry)
- **Tags:** mcp, registry, catalog, discovery, server-json
- **Repository:** https://github.com/modelcontextprotocol/registry

## Is Model Context Protocol Registry open source?

Yes — MIT-licensed.

## How much does Model Context Protocol Registry cost?

It is free to use.

## Can I self-host Model Context Protocol Registry?

Yes — it can be self-hosted.


---

The official Model Context Protocol Registry is the reference implementation for cataloging MCP servers so autonomous orchestrators can search, filter, and inspect registered tools programmatically.

## Why it matters for agents

It defines two things this registry adopts as conventions:

- The **`server.json` entry schema** — reverse-DNS `name`, `title`, dense `description`, `version`, `repository`, `packages[]` (with SHA-256 provenance), `remotes[]`, and a `_meta` reverse-DNS extension object for non-standard metadata.
- A **stateless REST read API** (`GET /v0.1/servers`) with cursor-based pagination via `metadata.nextCursor` and RFC 3339 `updated_since` delta filtering, so agents re-sync only what changed.

## Notes

This is an executable-server registry (publishers submit runnable MCP servers). The GTM Stacker registry reuses its `server.json` shape for *curated* tool entries but records upstream provenance rather than hosting or signing artifacts.