protogrid

Search / one.zovo/crx-permission-risk

crx-permission-risk

R0· no sign-in

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

v1.0.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust79of 100
Uptime, 30 days95%
Latency p50164 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "crx-permission-risk": {
      "type": "http",
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
claude mcp add --transport http crx-permission-risk https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp
[mcp_servers.crx-permission-risk]
url = "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "crx-permission-risk": {
      "type": "remote",
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "crx-permission-risk": {
      "type": "http",
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=crx-permission-risk&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vY3J4LXBlcm1pc3Npb24tcmlzay1tY3AubGlwbWljaGFsLndvcmtlcnMuZGV2L21jcCJ9"
}
{
  "servers": {
    "crx-permission-risk": {
      "type": "http",
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
{
  "mcpServers": {
    "crx-permission-risk": {
      "httpUrl": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
extensions:
  "crx-permission-risk":
    enabled: true
    name: "crx-permission-risk"
    type: streamable_http
    uri: "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: analyze_manifest (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); explain_permission (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); compare_permission_sets (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
  • pass
    tools.token_costabout 433 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 433 tokens to load them all · tool set e6e967f170e2 · checked 2026-10-19 12:00 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 79 / 100

no-repository
provenance55
liveness98
freshness85
hygiene80

+dns-namespace +website +reachable +uptime-95% ~updated-71d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp streamable-httpnoneyes95%164 ms2025-06-182026-10-19

Tools (3)

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

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "one.zovo/crx-permission-risk",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://zovo.one/",
  "description": "Score the privilege a Chrome MV3 extension takes from its manifest, and diff permission sets."
}