MCP Server Security

Building an approved MCP server catalog

An approved MCP server catalog is a maintained list of servers your company has reviewed, with owners, versions, allowed tools and a review date, enforced through the client's own allowlist settings. The public MCP Registry verifies namespaces but not code, so approval stays with you. Sources were read on 16 Nov 2026.

Facts read on .

How do you run an MCP registry for your company?

Run it as a maintained list that points to reviewed servers, using the public registry's metadata format as a model. The MCP Registry stores a server.json with the server's unique name, where to locate it (a package name or remote URL), execution instructions and discovery data, and it says downstream aggregators can add security checks, ratings or review.

A company catalog is that review layer. Keep it in version control so every addition is a reviewed change with an author and a date.

Name entries consistently. The public registry uses reverse-DNS style names such as io.github.user/server-name, tied to a verified GitHub account or domain, and mirroring that convention makes it simple to map an internal entry to its public origin.

Sources: MCP Registry: About.

Who approves a server?

A security reviewer approves a server, a named owner stays accountable for it and the requester never approves their own request. Splitting the roles keeps the catalog from becoming a rubber stamp.

Vendors describe the same workflow in their products: Noma Security says it provides an MCP registry where servers are approved, reviewed or blocked, and Snyk documents an Allowed MCP Servers classification where unlisted servers show as Not Allowed.

Keep the approval record in the same repository as the catalog. A pull request that names the reviewer, links the review report and shows the diff of tool definitions gives you the audit trail an auditor will ask for, and a request with no named owner should be refused, because an unowned server is the first one left unpatched.

Sources: Noma Security: MCP security; Snyk documentation: MCP Governance.

How do you enforce the catalog on developer machines?

Enforce it through the client's administrator settings and, where you need more, an endpoint tool. Claude Code documents allowedMcpServers and deniedMcpServers settings and a managed-mcp.json file for exclusive control of the servers available, and Cursor documents an MCP Allowlist with command entries for local stdio servers, URL entries for remote servers and tool allowlists.

Check the defaults. Snyk's documentation says its allowlist ships empty and disabled, and Cursor's tool allowlist allows all tools from a server when left empty. An unset list approves nothing and blocks nothing.

Tool-level lists matter because one approved server can expose many tools. Cursor lets an administrator restrict which tools of an approved server run automatically, so approve read tools first and hold write and delete tools for a separate review.

Sources: Claude Code documentation: Connect Claude Code to tools via MCP; Cursor documentation: Model Context Protocol; Snyk documentation: MCP Governance.

What should each catalog entry record?

Each entry should record enough to repeat the review and to detect drift. Fields that earn their place are:

Sources: MCP Registry: About; OWASP MCP Security Cheat Sheet.

How often should entries be re-reviewed?

Re-review on every change to the tool definitions and on a fixed calendar interval you set. OWASP asks for monitoring of tool descriptions after installation and for consent to be requested again when definitions change, and an entry whose hash no longer matches should drop out of the allowed set until someone reviews the difference.

Sources: OWASP MCP Security Cheat Sheet.

Sources