
Official MCP Registry Public servers, your approval
Argent Strategic Intelligence reads the protocol's public registry of MCP servers and imports each one switched off, so your admins choose what agents may use and the MCP Gate governs every call.
Start from the public catalog of MCP servers
The MCP Registry is the protocol's own public list of servers. Its maintainers launched it in preview in September 2025 as "an open catalog and API for publicly available MCP servers" (MCP blog).
Connect it to Argent and your admins can browse what is published, pick the servers they want, and bring them in without trusting any of them by default.
Discovery from the public list. Trust only from your own approval.
What Argent does with the Official MCP Registry
| Step | What happens |
|---|---|
| Read | Argent reads the registry's server list (GET /v0/servers), page by page. No account is needed. |
| Import | Each server becomes a record in your tenant, switched off and pending approval, with its publisher and description filled in from the registry. |
| Shape | A server with a remote address comes in as an HTTP server. A server published only as a package comes in as a local server that needs its launch command before it can run. |
| Large catalogs | The public registry is large, so one sync reads a fixed number of pages. If more remain, the sync says so and is never reported as the whole catalog. |
| Repeat | Syncing again adds new servers only and never changes one you already approved. |
Nothing imported is trusted
A server imported from the Official MCP Registry arrives switched off. The gateway will not broker a single call to it until an admin approves it.
- Approve or deny. The MCP registries page lists every imported server waiting for a decision. Approve enables it and lets the admin pick exactly which of its tools are allowed; Deny keeps it off.
- Every tool measured. Once a server is approved, Argent runs the MCP handshake, reads its full tool list and stores a fingerprint of each tool's definition. A tool whose definition later changes is marked as drifted, and the change is audited.
- Poisoned descriptions flagged. A built-in scanner checks each tool description for injection phrases, path rules and look-alike characters, and reports what it found without copying the text.
- Then the normal gate. An approved tool still needs a permission per agent on the MCP Gate page. See MCP servers.
How it connects
Argent reads the Official MCP Registry from its own control plane, outbound only, through the same guarded connection every Argent integration uses.
- One address. Registry URL: the registry's base address. Argent adds the
/v0/serverspath itself. - Safe outbound connection. The fetch uses Argent's shared outbound connection, which requires modern encryption and refuses internal addresses, so a registry address cannot be used to reach your internal systems.
- Honest failures. A fetch that fails reports a short reason and imports nothing. It never shows a registry as reachable when it is not.
- Per tenant. Every imported server is stamped with your tenant; tenants never see each other's imports.
What you configure
An admin connects the Official MCP Registry in the Argent console under Integrations, MCP registries.
- Add the connector and give it the address. Test checks the settings; turn on the live read option to have Test fetch the catalog too.
- Sync. One click fetches the catalog and imports each new server as pending approval. The result reads, for example, "Imported 12 (pending approval)".
- Approve what you want. Approve a server and choose which of its tools are allowed; deny the rest.
- Grant and watch. Give agents permission on the MCP Gate page, start the MCP Gate in watch mode, then switch it to Enforce.
Syncing again later adds only new servers. A server you already approved or curated is left exactly as you set it.
Where this fits
- Integration: MCP servers, the gate every imported server ends up behind.
- Other sources of servers: Docker MCP Catalog, the internal MCP registry.
- Capabilities: agent reach control, prompt injection defense, shadow AI discovery, watch before you enforce.
- Goals: threat defense, see all AI in your company.
- Use case: controlling agent tool access.
Browse all integrations.
Want this running on your own use cases?
Book a demo