Loading the registry…
Add your description here
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-chrome
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
2 findings · 9.5s
v0.3.74
8 findings · 1.1s
v0.1.0
0 findings · 3.7s
v0.1.0
0 findings · 3.7s
v0.71.0
3 findings · 0.2s
v2.3.8
3 findings · 1.6s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 19, 2026 | Flagged68 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 16 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 3 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
1 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: AAK-ANTHROPIC-SDK-001 · Files: test_chrome_mcp.py · reported by agent-audit-kit
The model could have called any of these a false positive and did not.
2 AAK-ANTHROPIC-SDK-001
Files: chrome_mcp_server.py, example_usage.py · reported by agent-audit-kit
1 AAK-DNS-REBIND-002
Files: requirements.txt · reported by agent-audit-kit
1 AAK-MCP-SDK-CVE-2026-52869-001
Files: requirements.txt · reported by agent-audit-kit
1 AAK-OAUTH-3P-001
Files: requirements.txt · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: pyproject.toml · reported by agent-audit-kit
1 CVE-2025-66416
Files: requirements.txt · reported by trivy
1 CVE-2026-52869
Files: requirements.txt · reported by trivy
1
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Artifact contains high-severity vulnerabilities and SDK risks.
The artifact contains high-severity vulnerabilities in its dependencies, including multiple CVEs and a DNS rebinding risk identified in `requirements.txt`, which could enable network access to internal services. Code in `chrome_mcp_server.py` and `example_usage.py` interacts with an Anthropic SDK, indicating potential network egress for API calls. A medium-severity finding related to third-party OAuth integration suggests credential handling and additional network communication. These findings warrant attention due to potential impacts on system integrity, data exposure, or unauthorized access.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Files: requirements.txt · reported by trivy
1 PYSEC-2026-1617
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/requirements.txt · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/requirements.txt · reported by osv-scanner