Crx Permission Risk

one.zovoPublished by zovo.onev1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Scores the privilege a Chrome MV3 extension requests in its manifest and compares permission sets between versions.

What you can do
This remote MCP server analyzes the manifest of a Chrome Manifest V3 extension and produces a privilege score for the permissions it requests. It can also diff two permission sets, showing what was added or removed between them. The registry description lists no individual tool names, so the exact tool surface is not documented here.
When to use it
Useful when reviewing a Chrome extension before installing or publishing it, or when checking whether an update quietly widened its permissions. It fits security review and extension-audit workflows rather than general browsing.
Requirements
A remote streamable HTTP endpoint; no package, runtime, account, API key, or environment variable is declared. Network access to the provider's endpoint is required.
Before you install
The manifest is sent to a third-party remote service, so extension manifests and permission data leave your machine. No authentication is declared, so anyone who knows the endpoint can call it. Treat the privilege score as advisory and verify findings against the manifest yourself.

Installation

In SourceWeft

  1. Open Crx Permission Risk in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/one.zovo%2Fcrx-permission-risk/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

3

analyze_manifest

Analyze a Chrome extension 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> web_accessible_resources). Content-script matches are counted as host access even when host_permissions is empty.

Parametersmanifestrequired

explain_permission

Explain one 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.

Parameterspermissionrequired

compare_permission_sets

Diff two 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 existing users until they re-accept.

Parametersafterrequiredbeforerequiredafter_hostsbefore_hosts

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.