Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.zhiqi-li/browser-mcp-cdp

NPM · BROWSER-MCP-CDP · SCANNED SEP 20

Local Chrome via CDP with profile-snapshot isolation and shared-broker multi-client support

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 545 tokens (~41/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "browser_evaluate" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.zhiqi-li/browser-mcp-cdp server?

io.github.zhiqi-li/browser-mcp-cdp runs locally as an npm package, launched with npx -y browser-mcp-cdp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · browser-mcp-cdp

# add to Claude Code
claude mcp add zhiqi-li-browser-mcp-cdp -- npx -y browser-mcp-cdp
// .cursor/mcp.json
{
  "mcpServers": {
    "zhiqi-li-browser-mcp-cdp": {
      "command": "npx",
      "args": [
        "-y",
        "browser-mcp-cdp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "zhiqi-li-browser-mcp-cdp": {
      "command": "npx",
      "args": [
        "-y",
        "browser-mcp-cdp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add zhiqi-li-browser-mcp-cdp -- npx -y browser-mcp-cdp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "zhiqi-li-browser-mcp-cdp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "browser-mcp-cdp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add zhiqi-li-browser-mcp-cdp --command npx --arg -y --arg browser-mcp-cdp
# ~/.hermes/config.yaml
mcp_servers:
  zhiqi-li-browser-mcp-cdp:
    command: "npx"
    args: ["-y", "browser-mcp-cdp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "zhiqi-li-browser-mcp-cdp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "browser-mcp-cdp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add zhiqi-li-browser-mcp-cdp -t stdio -c npx -a -y browser-mcp-cdp
// mcp.json
{
  "mcpServers": {
    "zhiqi-li-browser-mcp-cdp": {
      "command": "npx",
      "args": [
        "-y",
        "browser-mcp-cdp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 11 Sept 26 +1
    • Security disclosure: fail → unverified functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/browser-mcp-cdp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~545 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
browser_click ~38

Click an element matched by a CSS selector. Returns true if found and clicked.

NameTypeReqDescription
selectorstringyesCSS selector for the element to click

No output schema declared.

No examples provided.

browser_click_at ~69

Click at an absolute (x, y) pixel coordinate on the page using real CDP mouse events. Pierces through iframes and ad overlays that block CSS-selector clicks.

NameTypeReqDescription
xstringyesHorizontal coordinate in CSS pixels
ystringyesVertical coordinate in CSS pixels

No output schema declared.

No examples provided.

browser_evaluate ~70

Execute JavaScript in the current page context and return the result. Use await_promise=true (default) for async expressions.

NameTypeReqDescription
await_promisestringSet to "false" to skip awaiting a returned Promise (default: true)
expressionstringyesJavaScript expression to evaluate

No output schema declared.

No examples provided.

browser_fill ~49

Set the value of an input, textarea, or select element matched by a CSS selector.

NameTypeReqDescription
selectorstringyesCSS selector for the form element
textstringyesValue to set

No output schema declared.

No examples provided.

browser_get_html ~38

Get the outer HTML of the page or a specific element.

NameTypeReqDescription
selectorstringCSS selector (optional, defaults to full page HTML)

No output schema declared.

No examples provided.

browser_get_text ~38

Get the visible text content of the page or a specific element.

NameTypeReqDescription
selectorstringCSS selector (optional, defaults to document.body)

No output schema declared.

No examples provided.

browser_get_url ~15

Get the current page URL.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_navigate ~36

Navigate the browser to a URL. Returns the final URL and page title.

NameTypeReqDescription
urlstringyesThe URL to navigate to

No output schema declared.

No examples provided.

browser_new_tab ~37

Open a new browser tab, optionally navigating to a URL.

NameTypeReqDescription
urlstringURL to open (default: about:blank)

No output schema declared.

No examples provided.

browser_screenshot ~22

Capture a screenshot of the current page. Returns a PNG image.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_scroll ~48

Scroll the page by a relative offset in pixels.

NameTypeReqDescription
xstringHorizontal scroll in px (default 0)
ystringVertical scroll in px (default 0)

No output schema declared.

No examples provided.

browser_tabs ~22

List all open browser tabs with their id, url, and title.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

browser_wait_for ~63

Wait until an element matching the CSS selector appears in the DOM. Returns true if found within the timeout, false otherwise.

NameTypeReqDescription
selectorstringyesCSS selector to wait for
timeout_msstringMax wait time in milliseconds (default 5000)

No output schema declared.

No examples provided.

Common questions

What is the io.github.zhiqi-li/browser-mcp-cdp server?

io.github.zhiqi-li/browser-mcp-cdp is listed in the public MCP registry as io.github.zhiqi-li/browser-mcp-cdp. Local Chrome via CDP with profile-snapshot isolation and shared-broker multi-client support. This page covers its npm package (browser-mcp-cdp).

Is the io.github.zhiqi-li/browser-mcp-cdp server safe to use?

io.github.zhiqi-li/browser-mcp-cdp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.zhiqi-li/browser-mcp-cdp server expose?

io.github.zhiqi-li/browser-mcp-cdp exposes 13 tools: browser_navigate, browser_evaluate, browser_screenshot, browser_click, browser_fill, and 8 more. Their descriptions and schemas cost roughly 545 tokens of context every time the server is loaded.

Is the io.github.zhiqi-li/browser-mcp-cdp server still maintained?

io.github.zhiqi-li/browser-mcp-cdp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.zhiqi-li/browser-mcp-cdp server under?

io.github.zhiqi-li/browser-mcp-cdp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.