mcp-registry/com.policylayer/registry · v1.0.0
As of 2026-10-24 05:55 UTC, the Policylayer Registry MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 8 minutes.
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.
Claude Code
claude mcp add --transport http policylayer-registry-mcp-server https://api.policylayer.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"policylayer-registry-mcp-server": {
"type": "http",
"url": "https://api.policylayer.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Handshake + tools/list takes ~1,623 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.policylayer%2Fregistry/fixes
{
"name": "check_mcp_server",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"server"
],
"properties": {
"server": {
"type": "string",
"description": "Registry slug, npm package name (e.g. @acme/mcp-server), remote URL, or server name."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_mcp_stack",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"servers"
],
"properties": {
"servers": {
"type": "array",
"items": {
"type": "object",
"required": [
"candidates"
],
"properties": {
"name": {
"type": "string",
"description": "Your label for this server (e.g. its config key) — echoed back on the result."
},
"candidates": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 5,
"description": "Identifiers to try in order: npm package name, registry slug, or remote URL. Most package-like first."
}
}
},
"maxItems": 25,
"description": "One entry per server in the stack."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_tool",
"description": "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?\"",
"inputSchema": {
"type": "object",
"required": [
"server",
"tool"
],
"properties": {
"tool": {
"type": "string",
"description": "Tool name as the server declares it."
},
"server": {
"type": "string",
"description": "Registry slug or npm package name of the server."
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.policylayer/registry"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.policylayer/registry"}) over MCP.
check_mcp_stack ~293 tokensget_change_events ~201 tokenscheck_mcp_server ~194 tokenssearch_registry ~179 tokenscheck_tool ~160 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.policylayer%2Fregistry?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.policylayer%2Fregistry?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.policylayer%2Fregistry.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.policylayer%2Fregistry.svg :target: https://glimind.com/server/mcp-registry%2Fcom.policylayer%2Fregistry?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:c18463217f121eb8…, first seen 2026-10-17, included at leaf 5650 of 56,848. Version history · verify what your client received.
Compare: most reliable security servers · most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-24 05:55 UTC, the Policylayer Registry MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 8 minutes.
Policylayer Registry MCP server advertises 5 tools, including check_mcp_server, check_mcp_stack, check_tool, get_change_events, search_registry.
Point your MCP client at this streamable-http endpoint: https://api.policylayer.com/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.