Dev, web & IT
Design, code, host and ship sites and internal tools, with an AI coding agent doing most of the typing.
The MCP Registry is the official, publicly readable catalog of metadata for public MCP servers, and it's still in preview. It checks who owns a namespace, not whether a server is safe. Treat a listing as a pointer to the publisher, not an endorsement.
The MCP Registry is the project’s official central store of metadata about publicly accessible MCP servers. Publishers describe each server in a standard server.json file, and the registry offers a REST API so MCP clients and directories can find servers. The project says the registry is in preview, so breaking changes or data resets may happen before general availability.
Server names use reverse-DNS namespaces, such as io.github.username/server or com.example/server. Publishers prove they own the namespace through GitHub, DNS or an HTTP challenge, so only the owner of a domain or GitHub account can publish under it. The registry stores metadata only. The server code itself lives in package registries such as npm, PyPI or Docker Hub, or at the publisher’s remote URL.
The registry is meant mainly for downstream aggregators, such as marketplaces. The project expects them to pull new metadata regularly but infrequently, for example once an hour, and to add their own curation or ratings. It doesn’t list private servers. For internal servers, the project suggests running a private registry.
You can look up a server by the domain or GitHub account it claims to come from and see how it installs before adding it to a client. Directories built on the registry share one naming scheme.
The registry deliberately leaves security scanning to package registries and downstream aggregators. A verified namespace shows who published a server, not that it’s safe or still maintained. Before connecting one, read the publisher’s own docs, check what access it asks for, and start with read-only scopes where they exist. Treat a listing as a pointer to the publisher, not an IonBin recommendation.
Design, code, host and ship sites and internal tools, with an AI coding agent doing most of the typing.
Hand repeat admin (receipts, logs, notices, handoffs) to workflows your agent can trigger.
| Tool in this entry | How agents connect |
|---|---|
| Claude | Agent platform MCPAPI/CLIFile import |
| GitHub | MCPAPI/CLIFile import |
Levels come from each tool's recorded, sourced compatibility. How the levels work.
Practitioner views are restated in our words and labeled as views, not measured results. Product facts come from official sources dated above.
IonBin's wiki isn't user-edited. Corrections go to our Directory Curator, who checks them against primary sources before anything changes. Spot something wrong or out of date on “What is the MCP Registry?”? Email us with a link to a primary source.
Suggest an edit by email or write to [email protected]