Playwright Debug MCP Server

playwright-debug-mcp npm v0.2.0

Published by lars-albinsson — 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.

MCP server for frontend debugging with Playwright - Debug web apps with AI assistance

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

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 − 7 = 93. 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:

PointsAdoption-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 2

high Dynamic evaluation of a non-literal value (dist/tools/inspection.js)MTC-SRC-010

In the server's implementation (`dist/tools/inspection.js:198`): Evaluating a runtime value as code (rather than a fixed literal) executes whatever reaches it — a direct RCE primitive, and almost never necessary in legitimate code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const fn = new Function(code); return fn(); } catch (e) {

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 dist/tools/inspection.js

high Dynamic code execution in server code (dist/tools/inspection.js)MTC-SRC-001

In the server's implementation (`dist/tools/inspection.js:66`): Evaluating strings as code is the most direct RCE primitive; if any tool input reaches it, the server executes attacker-chosen code. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const fn = new Function('root', 'depth', 'maxDepth', `return ${summarizer}(root, depth, maxDepth)`);

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 dist/tools/inspection.js

Tools 39

Each tool and what it can reach — statically extracted from the published source.

  • audit_accessibilityno sensitive capability
  • clear_consoleno sensitive capability
  • clear_networkno sensitive capability
  • clickno sensitive capability
  • collect_component_instancesno sensitive capability
  • detect_memory_leaksno sensitive capability
  • evaluate_jsno sensitive capability
  • explain_errorno sensitive capability
  • fillno sensitive capability
  • find_componentno sensitive capability
Show 29 more tools ↓
  • find_hydration_errorsno sensitive capability
  • get_aria_treeno sensitive capability
  • get_component_stateno sensitive capability
  • get_consoleno sensitive capability
  • get_context_valuesno sensitive capability
  • get_debug_summaryno sensitive capability
  • get_domno sensitive capability
  • get_elementno sensitive capability
  • get_error_boundariesno sensitive capability
  • get_networkno sensitive capability
  • get_react_query_cacheno sensitive capability
  • get_react_treeno sensitive capability
  • get_redux_stateno sensitive capability
  • get_render_countno sensitive capability
  • get_request_detailno sensitive capability
  • get_slow_componentsno sensitive capability
  • get_text_contentno sensitive capability
  • get_web_vitalsno sensitive capability
  • get_zustand_storesno sensitive capability
  • go_backno sensitive capability
  • go_forwardno sensitive capability
  • hoverno sensitive capability
  • navigateno sensitive capability
  • reloadno sensitive capability
  • screenshotno sensitive capability
  • scrollno sensitive capability
  • selectno sensitive capability
  • typeno sensitive capability
  • wait_forno sensitive capability

What this scan could not see

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.

VersionScoreFindingsEngineScanned
v0.2.0 latest A 93/100 2 1.13.0 2026-09-07

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.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/playwright-debug-mcp/badge.svg)](https://mcptrustchecker.com/registry/playwright-debug-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/playwright-debug-mcp"><img src="https://mcptrustchecker.com/registry/playwright-debug-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/playwright-debug-mcp/badge.json via https://img.shields.io/endpoint?url=…

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-debug-mcp --online

Use the free API → How scoring works

More in Security & Testing