Chrome Devtools (ChromeDevTools) MCP Server
chrome-devtools-mcp
npm
v1.8.0
Source verified
Published by chromedevtools — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
MCP server for Chrome DevTools
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Hardcoded Google API key in server code MTC-SRC-008 | exfiltration |
2. Client adoption risk — 99 − 6 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
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 a deduction.
Findings 6
high Shell/command execution in server code (build/src/bin/check-latest-version.js)MTC-SRC-002
In the server's implementation (`build/src/bin/check-latest-version.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: { execSync } from 'node:child_process'; import fs from 'node:fs/promises'; import path from 'node:path'; import 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/bin/check-latest-version.js
high Shell/command execution in server code (build/src/browser.js)MTC-SRC-002
In the server's implementation (`build/src/browser.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: { execSync } from 'node:child_process'; import fs from 'node:fs'; import os from 'node:os'; import path from 'node:path'
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/browser.js
high Shell/command execution in server code (build/src/daemon/client.js)MTC-SRC-002
In the server's implementation (`build/src/daemon/client.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: rt { spawn } from 'node:child_process'; import fs from 'node:fs'; import net from 'node:net'; import { PipeTransport } f
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/daemon/client.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: rt { spawn } from 'node:child_process'; import { fileURLToPath } from 'node:url'; import { logger } from '../utils/logge
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
high Shell/command execution in server code (build/src/utils/check-for-updates.js)MTC-SRC-002
In the server's implementation (`build/src/utils/check-for-updates.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: : Apache-2.0 */ import child_process from 'node:child_process'; import fs from 'node:fs/promises'; import os from 'node
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/utils/check-for-updates.js
low Hardcoded Google API key in server code (build/src/tools/performance.js)MTC-SRC-008
A hardcoded Google API key (a public Firebase/web API key) appears in `build/src/tools/performance.js:190`. Verify whether this is a real credential; if so, remove and rotate it.
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
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 3
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 |
|---|---|---|---|---|
v1.8.0 latest |
A 93/100 | 6 | 1.13.0 | 2026-08-27 |
v1.7.0 |
A 93/100 | 6 | 1.13.0 | 2026-08-25 |
v1.6.0 |
A 93/100 | 6 | 1.12.1 | 2026-07-27 |
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 chrome-devtools-mcp --onlineOther implementations of Chrome Devtools 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.
Chrome DevTools automation with stealth mode support.
Chrome DevTools MCP server with Streamable HTTP transport for multi-agent sharing
More in Data Science & ML
MCP server for 2s.io — 575+ pay-per-call tools for AI agents — ground-truth data, AI gateway, and agent infra (storage, locks, queues, watchers). x402 USDC on Base/Solana, no API keys, upto usage billing, free trials.
ArXiv preprints + Google Scholar papers, with citation counts in one query.
Add MCP servers to your favorite coding agents with a single command.
Help agents automatically write and test stories for your UI components
Model Context Protocol server for AI-Archive platform - enables AI agents to discover, submit, and review research papers
MCP server for Semantic Scholar research workflows with stdio and Streamable HTTP transports.