com.policylayer/registry
REMOTE · API.POLICYLAYER.COM · SCANNED SEP 22
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 676 tokens (~135/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.policylayer/registry MCP server?
com.policylayer/registry is a hosted endpoint at https://api.policylayer.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.policylayer.com
claude mcp add --transport http com-policylayer-registry 'https://api.policylayer.com/mcp'
{
"mcpServers": {
"com-policylayer-registry": {
"url": "https://api.policylayer.com/mcp"
}
}
} {
"servers": {
"com-policylayer-registry": {
"type": "http",
"url": "https://api.policylayer.com/mcp"
}
}
} [mcp_servers.com-policylayer-registry] url = "https://api.policylayer.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-policylayer-registry": {
"type": "remote",
"url": "https://api.policylayer.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-policylayer-registry --url 'https://api.policylayer.com/mcp' --transport streamable-http
mcp_servers:
com-policylayer-registry:
url: "https://api.policylayer.com/mcp" {
"McpServers": {
"com-policylayer-registry": {
"Transport": "http",
"Url": "https://api.policylayer.com/mcp"
}
}
} assistant mcp add com-policylayer-registry -t streamable-http -u 'https://api.policylayer.com/mcp'
{
"mcpServers": {
"com-policylayer-registry": {
"type": "http",
"url": "https://api.policylayer.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://api.policylayer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.policylayer.com | CN=YR1,O=Let's Encrypt,C=US | 11 Aug 2026 | 9 Nov 2026 | RSA 2048 | SHA256-RSA | 5fecc6585a55f4ddb94f593c88e1f120fa8 |
| SANs: api.policylayer.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.policylayer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| policylayer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.policylayer.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.policylayer.com/mcp | HTTPS enforced | 301 | https://api.policylayer.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_mcp_server ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | Registry slug, npm package name (e.g. @acme/mcp-server), remote URL, or server name. |
No output schema declared.
No examples provided.
check_mcp_stack ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| servers | array | yes | One entry per server in the stack. |
No output schema declared.
No examples provided.
check_tool ~95
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| server | string | yes | Registry slug or npm package name of the server. |
| tool | string | yes | Tool name as the server declares it. |
No output schema declared.
No examples provided.
get_change_events ~134
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after_id | number | – | Return events with id greater than this cursor (default 0). |
| limit | number | – | Max events (1-1000, default 200). |
| severity | string | – | Minimum severity: that level and above. |
No output schema declared.
No examples provided.
search_registry ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max matches to return (1-20, default 10). |
| query | string | yes | Substring to match against slug, name and packages. |
No output schema declared.
No examples provided.
What is the com.policylayer/registry MCP server?
com.policylayer/registry is an MCP server listed in the public MCP registry as com.policylayer/registry. The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install. This page covers its hosted endpoint (https://api.policylayer.com/mcp).
Is the com.policylayer/registry MCP server safe to use?
com.policylayer/registry scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.policylayer/registry MCP server expose?
com.policylayer/registry exposes 5 tools: check_mcp_server, check_mcp_stack, search_registry, check_tool, get_change_events. Their descriptions and schemas cost roughly 594 tokens of context every time the server is loaded.
Does the com.policylayer/registry MCP server require authentication?
No. We connected to com.policylayer/registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.policylayer/registry MCP server still maintained?
com.policylayer/registry is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.