DebuggerSAFE
An MCP server exposing full Chrome DevTools Protocol debugging: breakpoints, step/run, call stacks, eval, and source maps.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
An MCP server that provides comprehensive Node.js debugging capabilities using the Chrome DevTools Protocol. This server enables AI assistants to debug Node.js applications with full access to breakpoints, stepping, variable inspection, call stacks, expression evaluation, and source maps.
Why use this MCP server?
This MCP server is useful when you need AI assistance with debugging Node.js applications. It provides programmatic access to all the debugging features you'd find in Chrome DevTools or VS Code, allowing AI assistants to help you set breakpoints, inspect variables, step through code, and analyze runtime behavior.
Features
- Full Node.js debugger: Set breakpoints, conditional breakpoints, logpoints, and pause-on-exceptions
- Stepping controls: Step over/into/out, continue to location, restart frame
- Variable inspection: Explore locals/closure scopes,
thispreview, and drill down into object properties - Expression evaluation: Evaluate JavaScript expressions in the current call frame with console output capture
- Call stack analysis: Inspect call stacks and pause-state information
- Source map support: Debug TypeScript and other transpiled code with full source map support
- Console monitoring: Capture and review console output during debugging sessions
Installation
npm install devtools-debugger-mcp
Configuration
Add the server to your MCP settings configuration:
{
"devtools-debugger-mcp": {
"command": "node",
"args": ["path/to/devtools-debugger-mcp/dist/index.js"]
}
}Alternatively, if installed globally, you can use the CLI binary:
{
"devtools-debugger-mcp": {
"command": "devtools-debugger-mcp"
}
}Node.js Debugging
This MCP server can debug Node.js programs by launching your script with the built‐in inspector (--inspect-brk=0) and speaking the Chrome DevTools Protocol (CDP).
How it works
start_node_debugspawns `
d4d424608358OBSERVED · 2026-10-02Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add devtools-debugger-mcp -- npx -y [email protected]
{
"mcpServers": {
"devtools-debugger-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (21)
14 read · 7 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
add_logpoint | write | |
blackbox_scripts | read | |
continue_to_location | read | |
evaluate_expression | read | |
get_object_properties | read | |
get_pause_info | read | |
get_script_source | read | |
inspect_scopes | read | |
list_call_stack | read | |
list_scripts | read | |
read_console | read | |
restart_frame | write | |
resume_execution | read | |
set_breakpoint | write | |
set_breakpoint_condition | write | |
set_exception_breakpoints | write | |
start_node_debug | write | |
step_into | read | |
step_out | read | |
step_over | read | |
stop_debug_session | write |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (3)
@modelcontextprotocol/sdk, chrome-remote-interface, ts-node, typescript, zod, @types/chrome-remote-interface, @types/node
An MCP server that provides comprehensive Node.js debugging capabilities using the Chrome DevTools Protocol. This server enables AI assistants to debug Node.js applications with full access to breakpo
Provides comprehensive Node.js debugging capabilities using the Chrome DevTools Protocol for full access to breakpoints, stepping, and code inspection.
Gates applied: no_behavioural_pass.
d4d424608358full audit observations/trust-audit/mcp-server/scriptedalchemy__debugger.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-02 | d4d424608358 | SAFE | B | 89 | first audit |
Questions
What is the Debugger MCP server?
An MCP server exposing full Chrome DevTools Protocol debugging: breakpoints, step/run, call stacks, eval, and source maps.
What tools does Debugger expose?
21 in total: 14 read-only, 7 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Debugger safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Debugger need?
No credential environment variables were found in its source, so it appears to need none.
How does Debugger run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as devtools-debugger-mcp at 0.0.1.
How current is this page?
The grade is for one exact copy of the source (d4d424608358), read on 2026-10-02. The repository is watched and re-audited when it changes.