mcpbeat Sign in

Crx Permission Risk MCP Server

answering

Crx Permission Risk is answering right now. Last checked 12 min ago. It exposes 3 tools.

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

Uptime history 87 days of history · worst day 93%
87 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
155 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Crx Permission Risk every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add crx-permission-risk --transport http https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.crx-permission-risk]
url = "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "crx-permission-risk": {
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "crx-permission-risk": {
      "type": "http",
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

analyze
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> web_accessible_resources). Content-script matches are counted as host access even when host_permissions is empty.
compare
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 existing users until they re-accept.
explain
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.

Endpoints

URLTransportStateLatencyChecked
https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp streamable-http answering 99 ms 12 min ago

Alternatives to Crx Permission Risk

same job, measured the same way
Chrome Web Store
by pipeworx-io

Chrome Web Store — public extension listing data: a single extension by id, free-text search, and…

395 installs/wk 47 tools answering
Markpin
by markpin

Search and read the web pages and highlights you saved with the Markpin Chrome extension.

107 installs/wk local only
Proving Lab
by provinglab

Cite or capture a web page; installs the capture extension in Firefox and Chrome.

10 tools answering
Chrome-Stats
by chrome-stats

Extension and app analytics across Chrome, Edge, Firefox, Google Play, and the Apple App Store.

answering
Chrome Extension Downloader
by extensiondownloader

Chrome extension data: free previews; API key for full reviews, comparisons and permissions.

16 tools answering
BrowserTap MCP
by linvireo

MCP server that drives the real Chrome you already use, through an extension and CDP.

111 installs/wk local only
Newton Browser
by koala-studios

Local-only Chrome and Edge control for MCP clients through an origin-scoped extension.

48 installs/wk local only
App & Game Store Data
by projectworks007

Apps, games and extensions with ratings and user reviews from app stores, Steam and Chrome.

answering

Crx Permission Risk — questions

Answers built from our own checks of this server.

What can Crx Permission Risk do?
It exposes 3 tools, read directly from the server on our last check. Among them: analyze_manifest, compare_permission_sets, explain_permission. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Crx Permission Risk working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 155 ms. The bar chart above shows every period we have measured.
How do I connect Crx Permission Risk?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Crx Permission Risk need an API key?
No. Crx Permission Risk completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Crx Permission Risk?
It answers our handshake in 155 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.