pulsemcp verified Safe content atomic mcp-remote

DevTools Debugger

This MCP server provides full Chrome DevTools Protocol debugging capabilities for Node.js applications, built by ScriptedAlchemy with comprehensive breakpoint management, stepping controls, call stack inspection, and variable evaluation. The implementation features advanced debugging tools including conditional breakpoints, logpoints, exception handling, scope analysis with object property inspection, and frame restart capabilities, all accessible through a clean API that supports both text and JSON output formats. Built with TypeScript and chrome-remote-interface, it includes robust pause state management with unique pause IDs, console output capture, script source retrieval, and blackbox pattern support, making it ideal for AI-assisted debugging workflows, automated testing scenarios, and development tools that need programmatic access to Node.js runtime inspection without manual DevTools interaction.

Cognium trust score

95%

Tier

Verified

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-19.

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

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: api-integration
Source: PulseMCP
Repository: github.com/scriptedalchemy/devtools-debugger-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve DevTools 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"