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.
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.
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.
Every record answers the question a catalog alone can't: is this server actually under enforcement? Each one carries a governance posture, so discovery comes with a verdict attached: governed (fronted by the gateway), not yet governed, or unknown.
The registry is the yellow pages; the gateway is the switchboard that enforces. A registry alone is discovery without governance; registry + gateway is governed discovery.
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.
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 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.
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.
