@rayven122/mcp-selenium
npm
v0.2.5
Source verified
Published by rayven122 — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Selenium WebDriver MCP Server (rayven122 fork — adds Edge IE mode)
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 − 6 = 94. 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 |
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.
Tool "execute_script" appears to run shell commands or evaluate code (parameter "script"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.
Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.
Location: tool execute_script
In the server's implementation (`bin/mcp-selenium.js:3`): 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: rt { spawn } from 'node:child_process'; import { dirname, resolve } from 'node:path'; import { fileURLToPath } from 'nod
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 bin/mcp-selenium.js
Tool "execute_script" takes a command-shaped parameter "script" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.
Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.
Location: tool execute_script · inputSchema.properties.script
Tool "execute_script" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool execute_script
Each tool and what it can reach — statically extracted from the published source.
execute_scriptruns code / shellupload_filenetwork egressadd_cookieno sensitive capabilityalertno sensitive capabilityclose_sessionno sensitive capabilitydelete_cookieno sensitive capabilitydiagnosticsno sensitive capabilityframeno sensitive capabilityget_cookiesno sensitive capabilityget_element_attributeno sensitive capabilityget_element_textno sensitive capabilityinteractno sensitive capabilitynavigateno sensitive capabilitypress_keyno sensitive capabilitysend_keysno sensitive capabilitystart_browserno sensitive capabilitytake_screenshotno sensitive capabilitywindowno sensitive capabilityScan 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.2.5 latest |
A 94/100 | 4 | 1.13.0 | 2026-09-07 |
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.
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 @rayven122/mcp-selenium --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 15 side by side →
Production-ready MCP server integrating Selenium 4 (BiDi) for browser automation
Selenium WebDriver MCP Server
Selenium WebDriver Model Context Protocol (MCP) server enabling AI agents and LLMs to control browsers
Selenium-based automation with 39 tools covering navigation, clicks, typing, assertions, screenshots, multi-session use, and page snapshots with stable element references and batched execution.
Selenium MCP server for browser automation, team-ready, MCP-compliant, and easy to share like Playwright MCP.
A Model Context Protocol (MCP) server for Selenium WebDriver automation with support for Chrome, Firefox, and Edge browsers
Model Context Protocol (MCP) server that integrates AgentQL data extraction capabilities.
Screenshot any URL or HTML as PNG/JPEG/WebP from your AI agent. Full-page, clean, no install.
MCP server for aria51 accessibility scanner
Bridge any browser web app to Claude Code via MCP
Browserbase’s official MCP server: cloud headless browsers for agents, with sessions and screenshots.
MCP server for AI web browser automation using Browserbase and Stagehand