Debugger (ai-capabilities-suite) MCP Server
@ai-capabilities-suite/mcp-debugger-server
npm
v1.5.23
Published by @ai-capabilities-suite — 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.
Enterprise-grade MCP server providing advanced debugging capabilities for Node.js and JavaScript applications via Chrome DevTools Protocol. Features 25+ debugging tools including breakpoints, variable inspection, execution control, CPU/memory profiling, h
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 6
high Tool "debugger_start" exposes command/code executionMTC-CAP-001
Tool "debugger_start" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool debugger_start
high Tool "debugger_detect_hang" exposes command/code executionMTC-CAP-001
Tool "debugger_detect_hang" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool debugger_detect_hang
medium Unconstrained command parameter "command" on "debugger_start"MTC-CAP-006
Tool "debugger_start" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool debugger_start · inputSchema.properties.command
medium Unconstrained command parameter "command" on "debugger_detect_hang"MTC-CAP-006
Tool "debugger_detect_hang" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool debugger_detect_hang · inputSchema.properties.command
low Mutating tool "debugger_start" declares no destructiveHintMTC-CAP-005
Tool "debugger_start" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool debugger_start
low Mutating tool "debugger_detect_hang" declares no destructiveHintMTC-CAP-005
Tool "debugger_detect_hang" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool debugger_detect_hang
Tools 29
Each tool and what it can reach — statically extracted from the published source.
debugger_detect_hangruns code / shelldebugger_startruns code / shelldebugger_add_watchno sensitive capabilitydebugger_continueno sensitive capabilitydebugger_get_global_variablesno sensitive capabilitydebugger_get_local_variablesno sensitive capabilitydebugger_get_performance_metricsno sensitive capabilitydebugger_get_stackno sensitive capabilitydebugger_get_watchesno sensitive capabilitydebugger_inspectno sensitive capability
Show 19 more tools ↓
debugger_inspect_objectno sensitive capabilitydebugger_list_breakpointsno sensitive capabilitydebugger_pauseno sensitive capabilitydebugger_remove_breakpointno sensitive capabilitydebugger_remove_watchno sensitive capabilitydebugger_set_breakpointno sensitive capabilitydebugger_set_exception_breakpointno sensitive capabilitydebugger_set_function_breakpointno sensitive capabilitydebugger_set_hit_count_conditionno sensitive capabilitydebugger_set_logpointno sensitive capabilitydebugger_start_cpu_profileno sensitive capabilitydebugger_step_intono sensitive capabilitydebugger_step_outno sensitive capabilitydebugger_step_overno sensitive capabilitydebugger_stop_cpu_profileno sensitive capabilitydebugger_stop_sessionno sensitive capabilitydebugger_switch_stack_frameno sensitive capabilitydebugger_take_heap_snapshotno sensitive capabilitydebugger_toggle_breakpointno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (29 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 |
|---|---|---|---|---|
v1.5.23 latest |
A 93/100 | 6 | 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 @ai-capabilities-suite/mcp-debugger-server --onlineOther implementations of Debugger 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Transparent proxy to debug, record, validate, and replay MCP (Model Context Protocol) sessions
MCP server for VS Code debugging via bridge extension
A Node.js application with Express and Newman for running and debugging Postman collections
More 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.