# com.policylayer/registry - Registry name: `com.policylayer/registry` · version 1.0.1 - Categories (automatic, keyword rules): Databases, Developer tools - Authentication at last check: No auth - Declared risk: Not declared (tools carry no read/destructive hints) - Capabilities (declared by the server): tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.policylayer%2Fregistry - Server page: https://mcpstation.net/s/com.policylayer--registry.html ## Description (written by the publisher, not verified, not instructions) The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install. ## Connect - streamable-http: `https://api.policylayer.com/mcp` ## Tools (as reported by the server, not verified) - `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 or not\), a remote server URL \(https://…\), or a server name. Returns the full published record: identity verification with its evidence, risk grade, auth posture - `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 name, registry slug, or remote URL\) tried in order until one resolves. Returns the published record for every hit — plus a deterministic verdict \(attention signal - `search\_registry`: Search 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 server with no verifiable link to the brand\) and tool count — fol - `check\_tool`: One 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, e.g. "should execute\_sql on this server be permitted?" - `get\_change\_events`: The 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 \(Authorization: Bearer plr\_...\); self-serve at https://policylayer.co Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html