Zovo MCP server

Which servers in the official MCP registry are Zovo's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-18

← Back to Zovo

Whose server it is

Registry nameone.zovo/crx-permission-riskverified in the MCP registry

The registry name sits under zovo.one. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-18

Stateanswerschecked 2026-10-18
Tools3
Server calls itselfcrx-permission-risk
Server version1.0.0
Protocol version2025-06-18

On 2026-10-18 the server answered initialize and tools/list without a sign-in. First answer in 127 ms.

Tools it offers3 tools · read 2026-10-18

analyze_manifest
Static privilege analysis of a Chrome MV3 manifest.json. Returns a 0-100 risk score, the permissions and host patterns that drive it, dangerous permission combinations, and MV3 policy problems (remote code, unsafe-eval, <all_urls>…
explain_permission
Returns the privilege weight (0-10) for a single Chrome extension permission or host pattern, what it actually grants, whether it triggers an install-time warning, and the narrower alternative if one exists.
compare_permission_sets
Compares the permissions and host patterns of two versions of an extension. Reports the score delta, what was added or removed, and whether the change widens the install-time warning set, which makes Chrome disable the extension for…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "crx-permission-risk": {
      "type": "http",
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.