io.github.BitePro/chrome-debugger-mcp

MCPcommunity
v1.0.4io.github.BiteProUnknownUpdated 6mo agonpmGitHub

Chrome breakpoint debugging MCP server for inspecting runtime values and stepping through code

Breakpoint-driven Chrome debugging for MCP clients. exposes Chrome DevTools Protocol debugging primitives as MCP tools. It lets an agent attach to a real Chrome tab, pause on breakpoints or , inspect scope variables, evaluate expressions inside the paused frame, step through code, and resume with runtime facts instead of guessing from static source. It is not a general browser automation server.…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
6mo agoLast update
Package
Authorio.github.BitePro
LicenseUnknown
Version1.0.4
Sourcemcp-registry
npmchrome-debugger-mcp
GitHubBitePro/chrome-debugger-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface18 tools · 2 privileged
Security scan✓ Cleanv1.0.4 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

18 tools · 2 privileged
Statically extracted from the published packagev1.0.4 · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

startDebuggingSessionNo description published

This tool published no description. Forge does not invent one.

launchChromeNo description published

This tool published no description. Forge does not invent one.

listTargetsNo description published

This tool published no description. Forge does not invent one.

connectNo description published

This tool published no description. Forge does not invent one.

disconnectNo description published

This tool published no description. Forge does not invent one.

setBreakpointNo description published

This tool published no description. Forge does not invent one.

removeBreakpointprivilegedNo description published

This tool published no description. Forge does not invent one.

waitForPauseNo description published

This tool published no description. Forge does not invent one.

waitForSpecificPauseNo description published

This tool published no description. Forge does not invent one.

getScopeVariablesNo description published

This tool published no description. Forge does not invent one.

evaluateprivilegedNo description published

This tool published no description. Forge does not invent one.

resumeNo description published

This tool published no description. Forge does not invent one.

stepIntoNo description published

This tool published no description. Forge does not invent one.

stepOverNo description published

This tool published no description. Forge does not invent one.

stepOutNo description published

This tool published no description. Forge does not invent one.

getStatusNo description published

This tool published no description. Forge does not invent one.

reloadPageNo description published

This tool published no description. Forge does not invent one.

forcePauseNo description published

This tool published no description. Forge does not invent one.

0 of 18 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Breakpoint-driven Chrome debugging for MCP clients. exposes Chrome DevTools Protocol debugging primitives as MCP tools. It lets an agent attach to a real Chrome tab, pause on breakpoints or , inspect scope variables, evaluate expressions inside the paused frame, step through code, and resume with runtime facts instead of guessing from static source. It is not a general browser automation server. The focus is runtime debugging. Demo: the agent launches Chrome, waits for a breakpoint, inspects…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

18 tools · 2 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.