Rhumb and the MCP Registry
The official MCP Registry is where a public MCP server's record is published: its name, version, address and packages. Its own docs call it a metadata repository in preview, meant to be read by downstream aggregators and not by an application directly. Rhumb is one of those readers: it reads the registry whole every day (see Sources and trust levels) and answers the question a record does not: for the system your agent works with, which server is its owner's own.
| Aspect | The MCP Registry | Rhumb |
|---|---|---|
| What it is | The official metadata repository for publicly accessible MCP servers, in preview. | An answer and a directory made from it, with other public records beside each server. |
| Who reads it | Aggregators and MCP clients, over its API. Its docs say host applications are not meant to read it directly. | A developer, or a coding agent over MCP, choosing what an agent connects. |
| Who publishes | A server's publisher, under a namespace authenticated through GitHub or by a DNS or HTTP check of a domain. | Nobody: nothing is published here. A server is a system's own when we named it so after reading its registry record, or it is published at the owner's own domain; a GitHub name alone never earns it. |
| An opinion | None by design: its docs call the metadata deliberately unopinionated, and leave ratings and curation to aggregators. | No rating either. One fixed rule in POST /v1/stack: a system's owner's own server or command-line tool, or word that there is none. |
| Security | Namespace checks, validation and takedowns. Scanning is left to package registries and aggregators. | What OSV lists against the exact version a record names, and a few fixed patterns over the tool definitions that were read, each with its date. A reading, never a review. |
| Beyond servers | Metadata for publicly accessible MCP servers; private ones are not supported. | Also a system's command-line tool, its owner's skills, the model to call and what the agent runs on, with a log of what changed. |
When the MCP Registry is the better fit
- You are building an MCP client or an aggregator and want every public server's record: read the registry itself, as we do.
- You have a server to publish: that is done there, with its own publisher tool. Nothing is submitted to Rhumb.
Architect an agentPick a modelRead the quickstart
What this page says about the MCP Registry was checked on 2026-11-15 against its own pages. Products change; if something here is out of date, tell us.