Webdriver MCP Server
mcp-server-webdriver
PyPI
v0.6.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
high Shell/command execution in server code (server.py)MTC-SRC-002
In the server's implementation (`server.py:130`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: try: out = subprocess.check_output( [executable, "--version"], stderr=subprocess.STDOUT, timeou
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server server.py
Tools 43
Each tool and what it can reach — statically extracted from the published source.
browser_upload_filenetwork egressbrowser_accept_dialogno sensitive capabilitybrowser_backno sensitive capabilitybrowser_clear_storageno sensitive capabilitybrowser_clickno sensitive capabilitybrowser_closeno sensitive capabilitybrowser_dismiss_dialogno sensitive capabilitybrowser_execute_jsno sensitive capabilitybrowser_fillno sensitive capabilitybrowser_find_elementsno sensitive capability
Show 33 more tools ↓
browser_forwardno sensitive capabilitybrowser_get_attributeno sensitive capabilitybrowser_get_cookiesno sensitive capabilitybrowser_get_sourceno sensitive capabilitybrowser_get_storageno sensitive capabilitybrowser_get_textno sensitive capabilitybrowser_get_titleno sensitive capabilitybrowser_get_urlno sensitive capabilitybrowser_hoverno sensitive capabilitybrowser_navigateno sensitive capabilitybrowser_openno sensitive capabilitybrowser_press_keyno sensitive capabilitybrowser_refreshno sensitive capabilitybrowser_screenshotno sensitive capabilitybrowser_scrollno sensitive capabilitybrowser_selectno sensitive capabilitybrowser_set_cookieno sensitive capabilitybrowser_set_storageno sensitive capabilitybrowser_set_viewportno sensitive capabilitybrowser_statusno sensitive capabilitybrowser_switch_frameno sensitive capabilitybrowser_waitno sensitive capabilitydevtools_clearno sensitive capabilitydevtools_computed_cssno sensitive capabilitydevtools_consoleno sensitive capabilitydevtools_css_variablesno sensitive capabilitydevtools_element_infono sensitive capabilitydevtools_enable_bidino sensitive capabilitydevtools_js_errorsno sensitive capabilitydevtools_network_allno sensitive capabilitydevtools_network_failedno sensitive capabilitydevtools_performanceno sensitive capabilitydevtools_reportno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (43 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.6.0 latest |
A 92/100 | 1 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-server-webdriver --online --registry pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.