Brutor MCP RegistryBETA

A governed enterprise subregistry on the official MCP registry specification (server.json 2025-12-11): federate the public ecosystem, publish your own servers with verified namespaces, and attach Brutor’s governance posture to every record — so what your agents discover is already inside policy.

Book Demo Download Free Trial

/what it does/

One subregistry, three jobs.

Federate

Mirror the public MCP ecosystem through one enterprise-controlled endpoint. A scheduled aggregator syncs connected registries incrementally — pulling only what changed, propagating removals — on the official spec, so standard clients just work.

Publish

Register your own MCP servers — internal tools, partner integrations — in the same discoverable catalog. Namespaces are verified (GitHub sign-in, DNS record, or HTTPS challenge), and published versions are immutable: a record can be deprecated with a reason, never silently rewritten.

Govern

Every record answers the question a catalog alone can’t: is this server actually under enforcement? Each one carries a governance posture — governed (fronted by the gateway), ungoverned, or unknown — so discovery comes with a verdict attached.

The registry is the yellow pages; the gateway is the switchboard that enforces. A registry alone is ungoverned discovery — registry + gateway is governed discovery.

/the chain/

Discover → authorize → authenticate → enforce.

Discovery is step one of a chain, not the destination. An agent finds a server in the registry, your policy decides whether it may use it, the gateway’s OAuth broker authenticates it without exposing tokens, and every tool call runs through guardrails, argument policies, and audit — the registry and gateway working as one system.

Built on the official MCP registry specification (server.json 2025-12-11, served on the standard /v0.1 API) — standard clients, no forks
Distinct from the in-gateway registry: this one federates and publishes across your whole estate
Records carry governance posture and verification state your policies can act on
Registers as an upstream too: other spec-compliant registries can federate from yours
Pairs with the gateway’s 80+ preconfigured, governed MCP servers

/inside the console/

Administered from the Gateway Admin Console.

No second login, no second UI. The registry is a section of the same Admin Console that runs the rest of your AI Control Plane — browse and search the federated catalog, publish and verify, manage upstream registry connections, and watch the registry’s own health, metrics and live logs.

The MCP Registry section of the Brutor Admin Console showing the Servers & Publish tab: a searchable multi-column gallery of MCP servers federated from the official registry, each card showing its namespace, publisher, verification badge, packages, remotes, downloads and version count, with Publish Server and per-server View Details actions. — **The federated catalog.** Public-ecosystem servers and your own publications in one searchable gallery — namespaces, verification badges, packages and remotes at a glance, tombstoned records a toggle away.

The server detail view for com.hubspot/hubspot-mcp-server in the Brutor Admin Console: lifecycle controls to move the server between active, deprecated and deleted, server icon management, server information with namespace, publisher and verification state, package distribution on NPM, and a version history with per-version deprecation. — **Full lifecycle on every record.** Move a server through active → deprecated → deleted with a status note consumers actually see, manage its icon and packages, and deprecate individual versions — published versions themselves stay immutable.

/run it yourself/

In the free trial — switched on at install.

The MCP Registry is in public beta and ships inside the Brutor free trial bundle: say yes when the installer asks, and the registry starts next to your gateway with the console section lit. The spec surface is stable, the governance metadata is still evolving, and beta capabilities are included at no extra charge while in beta.

Self-hosted, like everything else

A single high-performance Rust service — the same stack as the Gateway Core — running in your own environment, on your own network, against your own PostgreSQL. The same deployment model as the rest of the Brutor AI Control Plane.

/start the conversation/

Put a governed front door on your MCP estate.

Download the free trial — enable the registry when the installer asks — or book a 30-minute demo and we’ll federate your server catalog live.

Book Demo Download Free Trial