Index / MCP servers / Crx Permission Risk

Crx Permission Risk MCP server

Connect Crx Permission Risk and your agent gets 3 tools, among them analyze_manifest, compare_permission_sets, explain_permission. It answers at https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.

Status
Answering
Tools
3
Reliability
6 of 6 checks
Response time
253 ms
Transport
streamable HTTP
Last checked
24 October 2026

Score the privilege a Chrome MV3 extension takes from its manifest, and diff permission sets.

Description as the publisher wrote it.

The 3 tools Crx Permission Risk offers

ToolWhat it does
analyze_manifestStatic 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> web_acces
Inputs: manifest
compare_permission_setsCompares 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 existin
Inputs: before, after, before_hosts, after_hosts
explain_permissionReturns 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.
Inputs: permission

Add Crx Permission Risk to your AI client

Every block below points at https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http crx-permission-risk https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "crx-permission-risk": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "crx-permission-risk": {
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "crx-permission-risk": {
      "type": "http",
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "crx-permission-risk": {
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "crx-permission-risk": {
      "serverUrl": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "crx-permission-risk": {
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Crx Permission Risk
version: 0.0.1
schema: v1
mcpServers:
  - name: Crx Permission Risk
    type: streamable-http
    url: https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "crx-permission-risk": {
      "httpUrl": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "crx-permission-risk": {
      "type": "http",
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "crx-permission-risk": {
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fcrx-permission-risk-mcp.lipmichal.workers.dev%2Fmcp&type=streamable_http&id=crx-permission-risk&name=Crx%20Permission%20Risk

Is Crx Permission Risk up right now?

It answered our last check on 24 October 2026 in 253 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Crx Permission Risk

Questions about Crx Permission Risk

How many tools does Crx Permission Risk have?

3, as returned by the server's own tools/list on 23 September 2026: analyze_manifest, compare_permission_sets, explain_permission.

Is Crx Permission Risk down?

It answered our last check on 24 October 2026 in 253 ms. Over 6 checks since 12 September 2026 it answered 6.

How do I add Crx Permission Risk to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Crx Permission Risk need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: one.zovo. Endpoint host: crx-permission-risk-mcp.lipmichal.workers.dev. ARD identifier: urn:air:one.zovo:mcp:crx-permission-risk. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.