com.policylayer/registry
com.policylayer/registry · v1.0.1
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.
MCPremoteno credentialsDeveloper toolsE-commerceDatabases
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 5 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 83/100
What it does: 5 tools · 5 read, 0 write · Developer tools, E-commerce, Databases
Test call get_change_events: needs a key: tool error: This tool requires a PolicyLayer Registry Licence key — pass it as "Authorization: Bearer plr_..." when connecting to th (1,003 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: 0
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://api.policylayer.com/mcpTools
5 tools listed at last check
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: identity verification with its evidence, risk grade, auth posturecheck_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 for every hit — plus a deterministic verdict (attention signalsearch_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 server with no verifiable link to the brand) and tool count — folcheck_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, e.g. "should execute_sql on this server be permitted?"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 (Authorization: Bearer plr_...); self-serve at https://policylayer.co
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/com.policylayer/registry)