MCP · Project
MCP Registry
MCP Registry indexes publisher-supplied metadata for discovering public MCP servers.
+ FollowBuilder facts
- Public API. The hosted v0.1 servers endpoint exposes paginated listings without an account token. Source ↗
- Artifact scope. The registry stores metadata and links to artifacts distributed elsewhere, such as npm, PyPI, or container registries. Source ↗
- Remote listings. A server can publish metadata for a publicly reachable remote endpoint without publishing an installable package. Source ↗
- Publisher access. Publishing requires namespace verification through GitHub OAuth, GitHub Actions OIDC, DNS, or HTTP, depending on the namespace. Source ↗
- Downstream catalogs. The registry is designed as an upstream feed for subregistries that supply their own curation or metadata. Source ↗
Sources checked
Publisher update ·
MCP Registry v1.8.9 ↗Incremental listing sync now selects indexed pagination keys before fetching full listing payloads.
Change timeline
0 storiesNo verified releases in this timeline yet.