one.zovo/crx-permission-risk
REMOTE · CRX-PERMISSION-RISK-MCP.LIPMICHAL.WORKERS.DEV · SCANNED AUG 9
Score the privilege a Chrome MV3 extension takes from its manifest, and diff permission sets.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 349 tokens (~116/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · crx-permission-risk-mcp.lipmichal.workers.dev
claude mcp add --transport http one-zovo-crx-permission-risk https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp
[mcp_servers.one-zovo-crx-permission-risk] url = "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"one-zovo-crx-permission-risk": {
"type": "remote",
"url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add one-zovo-crx-permission-risk --url https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp --transport streamable-http
mcp_servers:
one-zovo-crx-permission-risk:
url: "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp" {
"mcpServers": {
"one-zovo-crx-permission-risk": {
"type": "http",
"url": "https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Aug 26 57
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 9 Aug 2026 · Probed https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lipmichal.workers.dev | CN=WE1,O=Google Trust Services,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 98275c7ccb0e6d340e2a98a08c778929 |
| SANs: lipmichal.workers.dev, *.lipmichal.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of crx-permission-risk-mcp.lipmichal.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://crx-permission-risk-mcp.lipmichal.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://crx-permission-risk-mcp.lipmichal.workers.dev/mcp | Served over HTTP | 200 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
analyze_manifest Analyze a Chrome extension manifest ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | – | yes | The manifest.json content, as a JSON object or a JSON string. |
No output schema declared.
No examples provided.
compare_permission_sets Diff two permission sets ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| after | array | yes | API permissions in the new version. |
| after_hosts | array | – | host_permissions in the new version. |
| before | array | yes | API permissions in the current published version. |
| before_hosts | array | – | host_permissions in the current published version. |
No output schema declared.
No examples provided.
explain_permission Explain one permission ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| permission | string | yes | A permission name such as cookies, or a host pattern such as <all_urls>. |
No output schema declared.
No examples provided.