Playwright Ui MCP Server
playwright-ui-mcp
npm
v1.0.1
Published by ailabs-393 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
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 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 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 |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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 4
high Tool "browser_evaluate" exposes command/code executionMTC-CAP-001
Tool "browser_evaluate" 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 browser_evaluate
medium Unconstrained command parameter "script" on "browser_evaluate"MTC-CAP-006
Tool "browser_evaluate" 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 browser_evaluate · inputSchema.properties.script
low Mutating tool "browser_evaluate" declares no destructiveHintMTC-CAP-005
Tool "browser_evaluate" 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 browser_evaluate
low Package runs install-time scripts (postinstall)MTC-SUP-010
"playwright-ui-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node dist/install.js && npx playwright install chromium || echo 'Note: Run npx playwright install chromium to install the browser'
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package playwright-ui-mcp
Tools 13
Each tool and what it can reach — statically extracted from the published source.
browser_evaluateruns code / shellbrowser_clickno sensitive capabilitybrowser_closeno sensitive capabilitybrowser_close_pageno sensitive capabilitybrowser_get_contentno sensitive capabilitybrowser_get_visible_elementsno sensitive capabilitybrowser_launchno sensitive capabilitybrowser_navigateno sensitive capabilitybrowser_new_pageno sensitive capabilitybrowser_screenshotno sensitive capability
Show 3 more tools ↓
browser_statusno sensitive capabilitybrowser_typeno sensitive capabilitybrowser_wait_forno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (13 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 |
|---|---|---|---|---|
v1.0.1 latest |
A 92/100 | 4 | 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 playwright-ui-mcp --onlineMore 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.