MCP.Market

Ts Debugger MCP server

by DigitalDefiance·io.github.DigitalDefiance/ts-mcp-debugger·v1.0.2

Enterprise debugging for Node.js/TypeScript with 25+ tools: breakpoints, profiling, hang detection

C65/100grade C
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
New

98 downloads/wk

Reviews

Write one

Nobody has reviewed Ts Debugger yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Ts Debugger tools (29, 6 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • debugger_add_watch

    Add an expression to the watch list. The expression will be evaluated each time the process pauses.

  • debugger_continue

    Resume execution of a paused debug session until the next breakpoint or program termination.

  • debugger_detect_hangwrite action

    Run a command and detect if it hangs or enters an infinite loop. Returns hang status, location, and stack trace if hung.

  • debugger_get_global_variables

    Get global variables accessible from the current scope with their names, values, and types.

  • debugger_get_local_variables

    Get all local variables in the current scope with their names, values, and types.

  • debugger_get_performance_metrics

    Get performance metrics including current memory usage, performance timeline, and leak detection.

  • debugger_get_stack

    Get the current call stack with function names, file locations (absolute paths), and line numbers.

  • debugger_get_watches

    Get all watched expressions with their current values. Reports value changes since the last pause.

  • debugger_inspect

    Evaluate a JavaScript expression in the current execution context and return the result with type information.

  • debugger_inspect_object

    Inspect an object by its object reference, returning properties with values. Handles nested objects and arrays up to a specified depth.

  • debugger_list_breakpoints

    Get all breakpoints for a debug session with their file, line, condition, and enabled state.

  • debugger_pause

    Pause a running debug session and return the current execution location.

  • debugger_remove_breakpointwrite action

    Remove a breakpoint from the debug session.

  • debugger_remove_watchwrite action

    Remove an expression from the watch list.

  • debugger_set_breakpoint

    Set a breakpoint at a specific file and line number. Optionally provide a condition.

  • debugger_set_exception_breakpoint

    Set an exception breakpoint to pause on caught and/or uncaught exceptions.

  • debugger_set_function_breakpoint

    Set a function breakpoint to pause when a function with the given name is called.

  • debugger_set_hit_count_condition

    Set a hit count condition for a breakpoint. The breakpoint will only pause when the condition is met.

  • debugger_set_logpoint

    Set a logpoint that logs a message without pausing execution. Use {variable} syntax for interpolation.

  • debugger_start

    Start a new debug session with a Node.js process. The process will be paused at the start.

  • debugger_start_cpu_profile

    Start CPU profiling for a debug session. Collects CPU profile data for performance analysis.

  • debugger_step_intowrite action

    Execute the current line and pause at the first line inside any called function.

  • debugger_step_outwrite action

    Execute until the current function returns and pause at the calling location.

  • debugger_step_overwrite action

    Execute the current line and pause at the next line in the same scope.

  • debugger_stop_cpu_profile

    Stop CPU profiling and return the profile data with bottleneck analysis.

  • debugger_stop_session

    Stop a debug session, cleanup all resources, and kill the process if still running.

  • debugger_switch_stack_frame

    Switch the execution context to a specific stack frame by index. Frame 0 is the top frame (current location).

  • debugger_take_heap_snapshot

    Take a heap snapshot for memory analysis. Returns memory usage report.

  • debugger_toggle_breakpoint

    Toggle a breakpoint between enabled and disabled states.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings
  • Code scan9 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancerepository not readable: repo not found3/15
  • Maintainer identityno repository or website to verify2/10
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Ts Debugger compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 20% of 48,255 servers
Tools
29
the typical server has 7
Tools that change things
21%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
98
more than 62% of 12,191 servers with a package

What its tools let an agent do: 23 read · 6 change

Install Ts Debugger in Claude Code, Cursor or VS Code

Runs npx -y @ai-capabilities-suite/mcp-debugger-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ts-mcp-debugger -- npx -y @ai-capabilities-suite/mcp-debugger-server
Add to Cursor

Ts Debugger: common questions

Is Ts Debugger MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Ts Debugger safety report
How do I install Ts Debugger?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Ts Debugger need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Ts Debugger maintained?
The latest release is v1.0.2.
How does Ts Debugger compare with other MCP servers?
safety score 65/100 (higher than 20% of 48,255 servers); tools 29 (the typical server has 7); tools that change things 21% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.