PolicyLayer MCP server
Which servers in the official MCP registry are PolicyLayer's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-17
- Registry namecom.policylayer/registryverified in the MCP registry
The registry name sits under policylayer.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-17
- Tools5
- Server calls itselfpolicylayer-registry
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-17 the server answered initialize and tools/list without a sign-in. First answer in 241 ms.
check_mcp_serverCheck an MCP server against the PolicyLayer registry BEFORE installing or allowing it. Accepts a registry slug, an npm package name (scoped or not), a remote server URL (https://…), or a server name. Returns the full published record…
check_mcp_stackCheck a whole MCP stack against the PolicyLayer registry in one call — up to 25 servers, each given as candidate identifiers (npm package name, registry slug, or remote URL) tried in order until one resolves. Returns the published record…
search_registrySearch the PolicyLayer registry of published MCP servers by name, slug or package substring. Returns candidate matches with risk grade, identity confidence (verified / unverified / mismatch — mismatch means it claims to be an official…
check_toolOne tool's full risk classification on a published MCP server: category, severity, risk analysis and evidence, OWASP classes, parameter schema and the recommended policy default. Use when deciding whether to allow a specific tool call…
get_change_eventsThe registry change feed: tool-surface drift, auth-posture flips, impostor flags, version bumps — every event the freshness watchers emit, id-cursored so a consumer resumes exactly where it stopped. Requires a Registry Licence key…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"registry": {
"type": "http",
"url": "https://api.policylayer.com/mcp"
}
}
}- com.policylayer/policylayeranswers, requires sign-inverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.