MCP Registry

The Brutor MCP Registry is a standalone registry server for Model Context Protocol servers — the answer to “which MCP servers exist, which are ours, and which are actually governed?” It implements the official MCP Registry specification (server.json 2025-12-11, served under the /v0.1 API), so any spec-compliant MCP client or tool can consume it directly.

It plays a different role from the gateway: the gateway enforces what a governed client may call; the registry is the catalog — discovery, publication and inventory. Together they close the loop: find a server in the registry, register it in the gateway, and its record flips to governed.

What sets it apart from pointing tooling at the public registry: federation (a scheduled aggregator serves upstream catalogs alongside your internal servers), publication (JWT-authenticated publishing with namespace verification and validation), and governance posture (every record says whether the server is governed, ungoverned or unknown).

The MCP Registry console inside the Admin Console: the Servers & Publish tab lists the registry’s servers as cards — namespace, version, publisher, transport, downloads and version count — with search, a deleted-records toggle and Publish Server.

The full documentation lives in its own section:

MCP Registry overviewWhat it is, what's in the box, and how it fits the platform.

Publishing serversserver.json publishing, validation, namespace verification.

Federation & the aggregatorServe upstream registries' catalogs as your own.

API referenceThe /v0.1 and /v0 surfaces, auth and _meta blocks.