PolicyLayer MCP Registry MCP server

An official MCP server from PolicyLayer that allows agents to vet other MCP servers before installation. It provides verified identity, risk grades, authentication posture, and tool classifications to ensure security. It supports single-server lookups, registry searches, tool-specific risk analysis, and change event monitoring to help agents make safe decisions about adding new tools.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by PolicyLayer

MCP endpoint (Streamable HTTP)

https://api.policylayer.com/mcp

Vendor documentation

What you can do with it

Check identity and risk grade of an MCP server before installation
Search the registry for published servers by name or slug
Analyze specific tool risk and OWASP classification
Monitor change events for posture flips or impostor flags

Tools advertised by the last live check:

check_mcp_server
check_mcp_stack
search_registry
check_tool
get_change_events

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http policylayer-mcp-registry https://api.policylayer.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add policylayer-mcp-registry --url https://api.policylayer.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable policylayer-mcp-registry in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "policylayer-mcp-registry": {
      "url": "https://api.policylayer.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "policylayer-mcp-registry": {
      "type": "streamableHttp",
      "url": "https://api.policylayer.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start policylayer-mcp-registry and inspect its tools.

VS Code configuration

{
  "servers": {
    "policylayer-mcp-registry": {
      "type": "http",
      "url": "https://api.policylayer.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http policylayer-mcp-registry https://api.policylayer.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "policylayer-mcp-registry": {
      "url": "https://api.policylayer.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "policylayer-mcp-registry": {
      "serverUrl": "https://api.policylayer.com/mcp"
    }
  }
}

See all 957

Do you run PolicyLayer MCP Registry?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing