Devtools Debugger MCP Server
devtools-debugger-mcp
npm
v0.0.1
Published by scriptedalchemy — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server exposing full Chrome DevTools Protocol debugging: breakpoints, stepping, call stacks, eval, and source maps. Also supports tab control, JS execution, screenshots, and network monitoring.
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 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 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 |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 3
high Shell/command execution in server code (dist/src/index.js)MTC-SRC-002
In the server's implementation (`dist/src/index.js:5`): 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: import { spawn } from 'child_process'; import CDP from 'chrome-remote-interface'; // Note: No debug trace wrappers; usi
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 dist/src/index.js
low Shell/command execution in packaging/dev tooling (dist/tests/node-debug-advanced.test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/tests/node-debug-advanced.test.js:3`): 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 CDP from 'chrome-remote-interface'; import path from 'node:path'; const s
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 dist/tests/node-debug-advanced.test.js
low Shell/command execution in packaging/dev tooling (dist/tests/node-debug.test.js)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`dist/tests/node-debug.test.js:3`): 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 CDP from 'chrome-remote-interface'; import path from 'node:path'; const s
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 dist/tests/node-debug.test.js
Tools 21
Each tool and what it can reach — statically extracted from the published source.
add_logpointno sensitive capabilityblackbox_scriptsno sensitive capabilitycontinue_to_locationno sensitive capabilityevaluate_expressionno sensitive capabilityget_object_propertiesno sensitive capabilityget_pause_infono sensitive capabilityget_script_sourceno sensitive capabilityinspect_scopesno sensitive capabilitylist_call_stackno sensitive capabilitylist_scriptsno sensitive capability
Show 11 more tools ↓
read_consoleno sensitive capabilityrestart_frameno sensitive capabilityresume_executionno sensitive capabilityset_breakpointno sensitive capabilityset_breakpoint_conditionno sensitive capabilityset_exception_breakpointsno sensitive capabilitystart_node_debugno sensitive capabilitystep_intono sensitive capabilitystep_outno sensitive capabilitystep_overno sensitive capabilitystop_debug_sessionno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (21 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
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.0.1 latest |
A 93/100 | 3 | 1.13.0 | 2026-09-09 |
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 devtools-debugger-mcp --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.