mcpbeat

Registry MCP Server

com.policylayer/registry
answering

Registry is answering right now. Last checked 5 min ago. It exposes 5 tools. Last commit 14 Jul 2026.

The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.

Uptime history 46 hours of history
46 hours agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
303 ms
Response time
average over 24h
1
Stars
last commit 14 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add registry --transport http https://api.policylayer.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "registry": {
      "url": "https://api.policylayer.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.registry]
url = "https://api.policylayer.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "registry": {
      "url": "https://api.policylayer.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "registry": {
      "url": "https://api.policylayer.com/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

mcp
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, freshness, and the tool surface listed riskiest-first. A server the registry does not know is queued for scanning by this very call — check back shortly.
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 signals and a suggested action) — and the lookup status for every miss; counts, grades and flagged tools come from the published records only. Costs one rate-limit unit per server.
change
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.com/registry/pricing.
registry
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 — follow up with check_mcp_server on the match you meant.
tool
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?"

Endpoints

URLTransportStateLatencyChecked
https://api.policylayer.com/mcp streamable-http answering 308 ms 5 min ago

Registry — questions

Answers built from our own checks of this server.

What can Registry do?
It exposes 5 tools, read directly from the server on our last check. Among them: check_mcp_server, check_mcp_stack, check_tool, get_change_events, search_registry. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Registry working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 303 ms. The bar chart above shows every period we have measured.
How do I connect Registry?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Registry need an API key?
No. Registry completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Registry?
It answers our handshake in 303 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Registry open source?
Yes — it is published under the MIT licence and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.