Remote MCP · Endpoint

com.policylayer/registry MCP server

No. com.policylayer/registry answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://api.policylayer.com/mcp

The last check completed an MCP handshake.

Registry name
com.policylayer/registry
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
130 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
The MCP server that vets MCP servers: identity, risk grade and per-tool risk before you install.
Website
https://policylayer.com/registry/mcp
Repository
https://github.com/PolicyLayer/mcp
Listing
From the official MCP registry (active).
Recent checks of com.policylayer/registry
CheckedResultHandshake
3 hours agoHandshake completed130 ms
1 day agoHandshake completed121 ms
2 days agoHandshake completed133 ms
3 days agoHandshake completed133 ms
4 days agoHandshake completed113 ms
5 days agoHandshake completed123 ms
7 days agoHandshake completed121 ms
9 days agoHandshake completed110 ms
12 days agoHandshake completed120 ms
14 days agoHandshake completed115 ms
16 days agoHandshake completed111 ms
18 days agoHandshake completed113 ms
20 days agoHandshake completed109 ms
23 days agoHandshake completed117 ms
25 days agoHandshake completed107 ms
26 days agoHandshake completed116 ms
28 days agoHandshake completed112 ms
29 days agoHandshake completed109 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.policylayer/registry and makes no claim about it beyond what these checks measured.