…/publisher
Publisher-declared: verification state, how the namespace was proven, and the receipt id for the rights verification. Attributable to a verified owner.
Positioning
A drop-in subregistry.
The MCP registry documents an open subregistry model: implement the read shape, add value through custom _meta fields, no approval step. RCX-Registry is exactly that — the same servers, the same request shape, plus verification and a signed history. Switching a client is a URL change.
Shape-compatible
Your existing clients work unchanged
The baseline read API mirrors the upstream /v0 surface field-for-field. Anything that already speaks to the official MCP registry speaks to this one — you get verification and receipts for free, without touching client code.
| GET /v0/servers | List servers — cursor pagination, limit |
| GET /v0/servers/{name}/versions | List versions for a server |
| GET /v0/servers/{name}/versions/{version} | Fetch one version |
The namespace contract
Everything RCX adds lives under one _meta key
Subregistries extend server entries through _meta, and RCX keeps its entire footprint inside org.rcxprotocol.registry. A client that ignores it sees a plain upstream entry; a client that reads it sees the proof.
{
"name": "com.example/my-mcp-server",
"version": "1.4.0",
"_meta": {
"org.rcxprotocol.registry/publisher": {
"verified": true,
"namespace_proof": "dns-txt",
"rights_receipt": "crown:8802…6f11"
},
"org.rcxprotocol.registry/auto": {
"last_snapshot": "crown:e6b1…88f2",
"mirrored_from": "registry.modelcontextprotocol.io"
}
}
}…/auto
Registry-derived: the snapshot receipt this entry was last seen in, and the upstream source it was mirrored from. Filled automatically, no publisher action needed.
Point a client here
VS Code, by policy
VS Code exposes an enterprise policy, McpGalleryServiceUrl, that repoints its entire MCP gallery at any spec-compliant endpoint. Because our /v0 matches the shape, this works today — one policy value moves a whole fleet onto a verified registry.
// VS Code enterprise policy (device management)
// Repoints the whole MCP gallery at a verified registry.
{
"McpGalleryServiceUrl": "https://registry.rcxprotocol.org"
}Any client that lets you configure the registry base URL points here the same way. And because there is a self-contained /openapi.json, OpenAPI-to-MCP tooling can wrap the registry itself as a server — one more surface, no extra work from us.
Freshness
Sync cadence
Mirror
A sync loop walks every upstream page on a fixed cadence and mints a signed snapshot over the Merkle root of the full set.
Soft-delete
When a server disappears upstream it is soft-deleted with a 30-day retention window — a removal is recorded, never a silent gap.
Enrichment
Publisher declarations refresh on a 24-hour cadence, each refresh hashed and receipted so capability metadata stays current and attributable.
Same servers. Same shape. Now with proof.
Repoint a client, or claim your namespace so your own entries carry the verified badge.