Chrome DevTools (Nimbus21) (nimbus21.ai) MCP Server
@nimbus21.ai/chrome-devtools-mcp
npm
v0.17.7
Published by @nimbus21.ai — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Chrome DevTools automation with stealth mode support.
Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:
| Points | What was found | Category |
|---|---|---|
| −22 | Hardcoded Google API key in server code MTC-SRC-008 | exfiltration |
Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind the deduction.
Findings 2
high Hardcoded Google API key in server code (build/src/tools/performance.js)MTC-SRC-008
A live-looking Google API key is hardcoded in `build/src/tools/performance.js:168`. Secrets in source ship to everyone who installs the package and are a direct credential leak.
Evidence: Google API key: AIza…(redacted)
Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.
Location: server build/src/tools/performance.js
high Shell/command execution in server code (build/src/telemetry/WatchdogClient.js)MTC-SRC-002
In the server's implementation (`build/src/telemetry/WatchdogClient.js:6`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server build/src/telemetry/WatchdogClient.js
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.17.7 latest |
C 78/100 | 2 | 1.5.0 | 2026-07-22 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @nimbus21.ai/chrome-devtools-mcp --onlineOther implementations of Chrome DevTools (Nimbus21) 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Drives Chrome through the Chrome DevTools integration.
Security scan results for the Chrome Devtools (ChromeDevTools) MCP server.
Security scan results for the Chrome Devtools (vibebrowser) MCP server.
More in Browser Automation
Security scan results for the 3dstreet MCP server.
Security scan results for the Accessibility Scanner MCP server.
Security scan results for the Adspower Browser MCP server.
Security scan results for the Agent Browser MCP server.
Security scan results for the Agent Browser MCP server.
Security scan results for the Agent Browser Mcp Codex MCP server.