io.github.frsorrentino/chrome-bridge
chrome-bridge
Borrow a tab from your own logged-in Chrome, hand it back; 2FA and CAPTCHA stay yours. 67 tools.
alive probed 2026-10-19
44tools
≈ 12ktokens, estimate
≈ 5.9 %of Claude's 200k window
8.3×the median server
437 msto initialize
30 msto list tools
- Run it
- npx -y chrome-bridge-mcp@1.30.5 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- chrome-bridge 1.30.5
- Capabilities
- tools
- Instructions
- 2 359 characters
- Of a 1M window
- ≈ 1.2 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/frsorrentino/chrome-bridge
- Registry
- active, updated 2026-10-17 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| network_rules | 512 | 4 % |
| scroll | 441 | 4 % |
| click | 411 | 3 % |
| fill_form | 398 | 3 % |
| wait_for | 380 | 3 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- This server is in the heaviest 10 % of the registry. Shorter descriptions, fewer optional parameters and fewer tools cut the cost. The command npx mcpcost --url <endpoint> --tools 50 lists every tool with its cost.
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.