Stealth Browser MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track browser engine and anti-bot compatibility while documenting action scope

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Browser automation on protected sites using local Chromium/CDP control.

What we know

A FastMCP browser-automation server using nodriver/CDP for navigation, extraction, network inspection and interaction.

Maintenance / activity evidence

Observed Sep 25, 2026 (UTC)Update NodeMaven sponsor banner and tracking links

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Browser/CDP session authority. Writes: Navigation; Form submission; Scripts; Uploads.
Optional HTTP bearer token
Sensitive access: Cookies, Authenticated pages, Local allowlisted files

Browser/CDP access can expose authenticated sessions and perform state-changing web actions.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

2,208 repository stars

Stars observed Oct 6, 2026.

A similarly named PyPI package exists, but identity binding was not strong enough for a public 30-day metric.

All limitations / Review context

Which browser actions and supported engine versions are currently documented?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Browser/CDP access can expose authenticated sessions and perform state-changing web actions.
Browser/CDP session authority.
Optional HTTP bearer token
Page/session/network data is visible to the server.
Reviewed write actions: Navigation; Form submission; Scripts; Uploads
Sensitive access: Cookies, Authenticated pages, Local allowlisted files
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Requires local Chrome/Chromium/Edge.
Remote HTTP exposure needs explicit authentication and network controls.

Original activity observations

2026-09-25T17:37:25Z: Update NodeMaven sponsor banner and tracking links

Technical identity

github.com/vibheksoni/stealth-browser-mcp

Exact implementation source: https://github.com/vibheksoni/stealth-browser-mcp ↗
Reviewed resource type: MCP Server
Repository identity: vibheksoni/stealth-browser-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
vibheksoni/stealth-browser-mcp
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Stealth Browser MCP controls a browser via MCP.
publisher documented step · Publisher instructions
git clone https://github.com/vibheksoni/stealth-browser-mcp.git cd stealth-browser-mcp python -m venv venv source venv/bin/activate pip install -r requirements.txt
publisher setup or prerequisite · Publisher instructions
pip install -r requirements.txt
Configure / authenticate
MCP100 setup guide
Clone repository, create Python venv, install requirements and register its `src/server.py` Python entry using publisher Claude add-json example.
Previously reviewed prerequisites / client guidance: macOS/Linux: configure Claude Code stdio using Python executable /ABSOLUTE/PATH/stealth-browser-mcp/venv/bin/python and script /ABSOLUTE/PATH/stealth-browser-mcp/src/server.py (official claude mcp add-json example). Windows uses venv\Scripts\python.exe. Python >=3.10 and installed Chrome/Chromium/Edge required. For HTTP transport set STEALTH_BROWSER_MCP_AUTH_TOKEN and bind securely. For HTTP exposure, publisher documents STEALTH_BROWSER_MCP_AUTH_TOKEN bearer protection; stdio local client does not require the same HTTP bearer setup.
Check connection
Suggested check
Invoke publisher `validate_browser_environment_tool()` for browser preflight.
Remove / uninstall / revoke
MCP100 setup guide
Remove Claude Code server registration `claude mcp remove stealth-browser-mcp` when installed under the README's name. Delete only the Python virtualenv/checkout after terminating its browser subprocesses; preserve your normal Chrome/Edge profiles.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove stealth-browser-mcp

Official Documentation & Sources

What it does

A FastMCP browser-automation server using nodriver/CDP for navigation, extraction, network inspection and interaction.

Capability: Browser Automation
Resource type: MCP Server
Best fit: Browser automation on protected sites using local Chromium/CDP control.

Representative uses

Navigate and interact with sites
Extract DOM/styles/assets
Inspect network traffic
Automate forms and allowlisted uploads

Limitations

Requires local Chrome/Chromium/Edge.
Remote HTTP exposure needs explicit authentication and network controls.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Optional HTTP bearer token
Permissions: Browser/CDP session authority.
Data handling: Page/session/network data is visible to the server.
Cost: free
Risk and cautions: Browser/CDP access can expose authenticated sessions and perform state-changing web actions.

Access scope and cautions

Write actions: Navigation Form submission Scripts Uploads
Sensitive access: Cookies Authenticated pages Local allowlisted files
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Navigate and interact with sites; Extract DOM/styles/assets; Inspect network traffic; Automate forms and allowlisted uploads.

What setup and authentication are documented?

Recorded installation/entrypoint step: pip install -r requirements.txt. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: STEALTH_BROWSER_MCP_AUTH_TOKEN; MCP_AUTH_TOKEN; BROWSER_FILE_UPLOAD_ALLOWED_DIRS. No configuration values are supplied here. Prerequisites: Python 3.10+; Chrome/Chromium/Edge. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Optional bearer token for HTTP.

Can it modify data or perform write operations?

Documented write actions include: Navigation; Form submission; Scripts; Uploads. Recorded permission boundary: Browser/CDP session authority.

What data-handling boundary should I consider?

Page/session/network data is visible to the server. Recorded sensitive-access context: Cookies; Authenticated pages; Local allowlisted files.

What limitations and risks should I check before use?

Browser/CDP access can expose authenticated sessions and perform state-changing web actions. Requires local Chrome/Chromium/Edge. Remote HTTP exposure needs explicit authentication and network controls. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

vibheksoni is listed as Community implementation in MCP100’s current evidence.