Registry MCP Server

by policylayer Your server? Claim it

answering

Registry is answering right now. Last checked 10 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 91 days of history · worst day 90%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

316 ms

Response time

average over 24h

Stars

last commit 14 Jul 2026

Nothing serious here today

Today is the operative word: we check Registry every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "registry": {
      "type": "http",
      "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

URL	Transport	State	Latency	Checked
https://api.policylayer.com/mcp	streamable-http	answering	335 ms	10 min ago

Alternatives to Registry

same job, measured the same way

KillerSkills

by cyligence-karim

Security verdicts for agent skills and MCP servers, from sandbox runs, before you install them.

2 291 installs/wk local only

Mcpgrade

by mcpgrade

Security grades (A-F) for MCP servers. Check one before you install or trust it. mcpgrade.dev

54 installs/wk local only

Veragent

by lixiaowww

Check the trust/security score of MCP servers, agents, skills & CLIs before you install them.

96 installs/wk local only

Mund — MCP Security Scanner

by tyox-all

Scan for prompt injection, secrets, PII, and vet MCP servers before installation

2 179 installs/wk local only

Stillos Ratings MCP

by stillmarcus24

Check an MCP server before you install it — outside-in trust ratings for 7,000+ operators.

local only

mcp-trust

by saagpatel

Check the danger grade of any public MCP server before you connect.

136 installs/wk local only

Pre-install canonical-identity verification

by textforagents

Pre-install canonical-identity verification for MCP servers and skills, with signed verdicts.

3 tools answering

SkillTriage

by moorai

Scan AI agent skills, MCP server packages and MCP configs before you install them. Static analysis.

4 tools answering

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 316 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 in the form 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 316 ms on average, which is faster than 45% 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?

The code is open source: it is published under the MIT licence and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at api.policylayer.com, which runs on its operator's own terms.