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.

BrowserTap MCP

PYPI · BROWSERTAP-MCP · SCANNED SEP 20

MCP server that drives the real Chrome you already use, through an extension and CDP.

Available components

+4 this week 79 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 36 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 5474 tokens (~99/item across 55 items; 55 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (96% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "uninstall_extension" implies "uninstall" 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 56 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 BrowserTap MCP server?

BrowserTap MCP runs locally as a PyPI package, launched with uvx browsertap-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · browsertap-mcp

# add to Claude Code
claude mcp add linvireo-browsertap-mcp -- uvx browsertap-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "linvireo-browsertap-mcp": {
      "command": "uvx",
      "args": [
        "browsertap-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "linvireo-browsertap-mcp": {
      "command": "uvx",
      "args": [
        "browsertap-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add linvireo-browsertap-mcp -- uvx browsertap-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "linvireo-browsertap-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "browsertap-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add linvireo-browsertap-mcp --command uvx --arg browsertap-mcp
# ~/.hermes/config.yaml
mcp_servers:
  linvireo-browsertap-mcp:
    command: "uvx"
    args: ["browsertap-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "linvireo-browsertap-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "browsertap-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add linvireo-browsertap-mcp -t stdio -c uvx -a browsertap-mcp
// mcp.json
{
  "mcpServers": {
    "linvireo-browsertap-mcp": {
      "command": "uvx",
      "args": [
        "browsertap-mcp"
      ]
    }
  }
}
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 +1

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

  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 9 Sept 26 +1

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

  • 7 Sept 26 +1

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

  • 5 Sept 26 +1

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

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 pypi/browsertap-mcp@0.4.12

Provenance No attestation

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

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 36 packages
Packages resolved 36
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 55 exposed · ~5,237 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
type_text ~174

Type text via the real keyboard, optionally after clicking a field at click_x/click_y in absolute virtual-desktop PHYSICAL screen pixels (see mouse_click for how that differs from the CSS pixels the page_* tools take); a click point on no display is refused with coordinates_off_screen. Pass session_id — the same one you pass every other tool (preferred) — and that tab is raised after the quiet check so the keystrokes go to it. Without one the current global target is raised, which another task may have changed. Approval may foreground the selected browser tab. activate_session='none' types into whatever already has focus.

NameTypeReqDescription
activate_session
click_x
click_y
intervalnumber
session_id
textstringyes

Structured output declared, but exposes no named fields.

No examples provided.

uninstall_extension ~70

Uninstall another installed extension by id. show_confirm_dialog defaults to true; set it false only for an explicitly selected disposable/test extension. The BTAP bridge cannot uninstall itself through its active connection.

NameTypeReqDescription
extension_idstringyes
session_id
show_confirm_dialogboolean

Structured output declared, but exposes no named fields.

No examples provided.

upload_files ~85

Set files on a file input, which JS cannot do (input.files is read-only). Give a CSS selector for the <input type=file> and absolute local paths. Runs as a single CDP batch so the DOM node ids stay valid across the sequence.

NameTypeReqDescription
pathsyes
selectorstringyes
session_id
timeoutnumber

Structured output declared, but exposes no named fields.

No examples provided.

wait_for ~149

Wait until a condition holds on the page, then return. Use this instead of polling scan_page (each scan re-serializes the whole DOM). Exactly one of selector / text / url_pattern / js must be given: selector waits for a CSS match, text for a substring in body text, url_pattern for a regex on the URL, js for a JS expression to become truthy. Polls inside the page, so it costs one bridge roundtrip regardless of how long the wait takes.

NameTypeReqDescription
goneboolean
js
selector
session_id
text
timeoutnumber
url_pattern

Structured output declared, but exposes no named fields.

No examples provided.

wait_for_url ~131

Wait for navigation to settle: blocks until the tab's URL matches url_pattern (regex, or plain substring) and — unless wait_ready=false — document.readyState is 'complete', then returns the final url, title and readyState. Use this after a click or open_url that navigates; wait_for(url_pattern=...) only checks the URL and can return while the new document is still blank. Polls in-page, so a long wait is still cheap.

NameTypeReqDescription
session_id
timeoutnumber
url_patternstringyes
wait_readyboolean

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the BrowserTap MCP server?

BrowserTap MCP is listed in the public MCP registry as io.github.LinVireo/browsertap-mcp. MCP server that drives the real Chrome you already use, through an extension and CDP. This page covers its PyPI package (browsertap-mcp).

Is the BrowserTap MCP server safe to use?

BrowserTap MCP scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 BrowserTap MCP server expose?

BrowserTap MCP exposes 55 tools: get_automation_profile, set_automation_profile, get_setup_status, list_tabs, list_all_tabs, and 50 more. Their descriptions and schemas cost roughly 5,237 tokens of context every time the server is loaded.

Is the BrowserTap MCP server still maintained?

BrowserTap MCP 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.