pulsemcp scanned Safe content atomic mcp-remote

Node.js Debugger

This Node.js debugger MCP server by qckfx provides programmatic debugging capabilities for AI agents through the Chrome DevTools Protocol, enabling full process lifecycle management and interactive debugging sessions. The implementation spawns Node.js processes with `--inspect-brk` debugging enabled, manages debug ports automatically, and exposes comprehensive debugging tools including breakpoint management, step-through execution, call stack inspection, and expression evaluation in debug contexts. Built with TypeScript and the chrome-remote-interface library, it handles the complexities of debugger attachment, execution state management, and provides both MCP tools for debugging operations and resources for session state monitoring, making it valuable for AI-assisted code debugging, automated testing workflows, and educational scenarios where agents need to understand code execution flow.

Cognium trust score

65%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-02.

Scan details: Circle-IR · 2026-09-02 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: ai-ml
Source: PulseMCP
Repository: github.com/qckfx/node-debugger-mcp
Author type: human
Last scanned: 2026-09-02
Updated: 2026-09-02

View source Find related skills

MCP

Resolve Node.js Debugger from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"