Turbo Browser MCP
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
New / early find
New / early find: first tested 2026-11-18 UTC. Turbo Browser MCP (npm turbo-browser-mcp 0.7.0, MIT; repo Tthanh2k6/turbo-browser-mcp, 130 GitHub stars when tested, created 2026-11-14 UTC) is a Playwright-based browser MCP built to cut agent turns and tokens (one-call form fill, compact DOM, batch actions). Installed with scripts off; initialize and tools/list over stdio succeeded with no credentials (11 tools). We ran it with --mode launch (its own clean headless Chromium; by default it first tries to attach to a Chrome on port 9222). Real calls: tabs_batch opened https://example.com, extract_clean_text returned the page text as markdown, inspect_compact listed the page's one link. Form-fill, JavaScript and cookie tools not called.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): pass. 3 of 3 real calls passed with no credentials. Evidence: local test run, Nov 18, 2026 UTC.
Transport (tested 2026-11-18 UTC): stdio
Token cost (estimate): approx. 3111 tokens, cl100k estimate (11 tools, measured 2026-11-18 UTC, version 0.7.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 1 read, 0 write (state-changing), 10 unclassified · Auth: local · Rate limit: unknown · Pricing unit: unknown
Auth: local. Rate limit: unknown. Pricing unit: unknown.
act_fast— unclassifiedbatch_actions— unclassifiedcapture_page— unclassifiedevaluate_js— unclassifiedextract_clean_text— unclassifiedinspect_compact— readnetwork_session— unclassifiedpage_diagnostics— unclassifiedsmart_fill_form— unclassifiedtabs_batch— unclassifiedwait_for_human— unclassified
local stdio server with no recorded cloud credential
Score 100/100 · Tools 11 · Token cost approx. 3,111 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 0.7.0 · Package turbo-browser-mcp · Repo Tthanh2k6/turbo-browser-mcp
Summary: Turbo Browser MCP completed an MCP handshake without credentials and exposed 11 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 11
- Context cost
- approx. 3111 tokens, cl100k estimate (11 tools, measured 2026-11-18 UTC, version 0.7.0; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install turbo-browser-mcp --ignore-scripts (Node v24.22.1, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 11 tools listed in 3.9s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 130 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 3111 tokens, cl100k estimate for 11 tools · about 38% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-18 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 11 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
c4d34eae9d25: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "turbo-browser-mcp",
"version": "0.7.0",
"registry": "npm",
"status": "working",
"tested": "2026-11-18",
"tools_count": 11,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install turbo-browser-mcp --ignore-scripts` (Node v24.22.1, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 11 tools listed in 3.9s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 130 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-18T03:44:52.524Z"
}Install
npx -y turbo-browser-mcp
Pin the version we tested
npx -y --ignore-scripts turbo-browser-mcp@0.7.0
tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"turbo-browser-mcp": {
"command": "npx",
"args": [
"-y",
"turbo-browser-mcp@0.7.0"
]
}
}
}Tools listed
tabs_batch, inspect_compact, smart_fill_form, act_fast, batch_actions, extract_clean_text, evaluate_js, page_diagnostics, capture_page, network_session, wait_for_human
Quick config
{
"mcpServers": {
"turbo-browser-mcp": {
"command": "npx",
"args": [
"-y",
"turbo-browser-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install turbo-browser-mcp --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-18 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (11 in our test).
{
"mcpServers": {
"turbo-browser-mcp": {
"command": "npx",
"args": [
"-y",
"turbo-browser-mcp"
]
}
}
}Test history
- 2026-11-18 UTC: New
Related: Troubleshooting: Protocol version mismatch (HTTP 400)
FAQ
Is Turbo Browser MCP deprecated?
No. Turbo Browser MCP was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces Turbo Browser MCP?
Nothing; Turbo Browser MCP is not deprecated as of 2026-11-18 UTC.
Does Turbo Browser MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 11 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.