Remote MCP · Endpoint

one.zovo/crx-permission-risk MCP server

No. one.zovo/crx-permission-risk answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
one.zovo/crx-permission-risk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
181 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Score the privilege a Chrome MV3 extension takes from its manifest, and diff permission sets.
Listing
From the official MCP registry (active).
Recent checks of one.zovo/crx-permission-risk
CheckedResultHandshake
1 hour agoHandshake completed181 ms
1 day agoHandshake completed176 ms
2 days agoHandshake completed118 ms
3 days agoHandshake completed124 ms
4 days agoHandshake completed101 ms
5 days agoHandshake completed119 ms
6 days agoHandshake completed150 ms
8 days agoHandshake completed118 ms
11 days agoHandshake completed142 ms
13 days agoHandshake completed140 ms
15 days agoHandshake completed146 ms
18 days agoHandshake completed92 ms
20 days agoHandshake completed271 ms
22 days agoHandshake completed112 ms
24 days agoHandshake completed102 ms
26 days agoHandshake completed86 ms
27 days agoHandshake completed111 ms
28 days agoHandshake completed132 ms
29 days agoHandshake completed349 ms

The last 19 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.

Listing data comes from the official MCP registry. Glide is not affiliated with one.zovo/crx-permission-risk and makes no claim about it beyond what these checks measured.