The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install. Connect the official Registry MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http registry-api https://api.policylayer.com/mcpRun in your terminal, then restart Claude Code.
Registry · https://api.policylayer.com/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “check_mcp_server”: Check an MCP server against the PolicyLayer registry BEFORE installing or allowing it. Accepts a registry slug, an npm package name (scoped.”
“Use “check_mcp_stack”: Check a whole MCP stack against the PolicyLayer registry in one call — up to 25 servers, each given as candidate identifiers (npm package na.”
“Use “search_registry”: Search the PolicyLayer registry of published MCP servers by name, slug or package substring. Returns candidate matches with risk grade, iden.”
“Use “check_tool”: One tool's full risk classification on a published MCP server: category, severity, risk analysis and evidence, OWASP classes, parameter sche.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Registry holds up.
Operated by Registry (policylayer.com) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Registry adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Registry in the gate directory. No sign-in needed.
Registry's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
check_mcp_server — Check an MCP server against the PolicyLayer registry BEFORE installing or allowing it. Accepts a registry slug, an npm package name (scoped
check_mcp_stack — Check a whole MCP stack against the PolicyLayer registry in one call — up to 25 servers, each given as candidate identifiers (npm package na
search_registry — Search the PolicyLayer registry of published MCP servers by name, slug or package substring. Returns candidate matches with risk grade, iden
check_tool — One tool's full risk classification on a published MCP server: category, severity, risk analysis and evidence, OWASP classes, parameter sche
get_change_events — The registry change feed: tool-surface drift, auth-posture flips, impostor flags, version bumps — every event the freshness watchers emit, i
https://api.policylayer.com/mcpYes — Registry operates its own remote MCP server at api.policylayer.com. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Registry in the directory. No account or sign-in is needed. From then on, Registry's tools are available in every client you've connected to gate.
No. Registry runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Registry in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Registry in: Claude · Claude Code · ChatGPT · Cursor · VS Code