Playwright Tools MCP Server

mcp-playwright-tools PyPI v2.1.0

Published by cuber-it — 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.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — 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 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([get_page_content, get_page_requests, wait_for_download]) co-exist with external-action tools ([upload_file]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [get_page_content, get_page_requests, wait_for_download] → sinks [upload_file]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow get_page_content → upload_file

Tools 73

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

  • get_page_contentingests untrusted input
  • get_page_requestsingests untrusted input
  • upload_filenetwork egress
  • wait_for_downloadingests untrusted input
  • abort_routeno sensitive capability
  • accept_dialogno sensitive capability
  • checkno sensitive capability
  • clearno sensitive capability
  • clear_cookiesno sensitive capability
  • clear_routeno sensitive capability
Show 63 more tools ↓
  • clear_storageno sensitive capability
  • clickno sensitive capability
  • click_by_roleno sensitive capability
  • click_by_textno sensitive capability
  • close_tabno sensitive capability
  • current_urlno sensitive capability
  • describe_elementno sensitive capability
  • dismiss_dialogno sensitive capability
  • double_clickno sensitive capability
  • drag_and_dropno sensitive capability
  • execute_scriptno sensitive capability
  • fillno sensitive capability
  • fill_by_labelno sensitive capability
  • find_by_labelno sensitive capability
  • find_by_placeholderno sensitive capability
  • find_by_roleno sensitive capability
  • find_by_test_idno sensitive capability
  • find_by_textno sensitive capability
  • find_interactive_elementsno sensitive capability
  • focusno sensitive capability
  • get_all_textsno sensitive capability
  • get_aria_snapshotno sensitive capability
  • get_attributeno sensitive capability
  • get_console_messagesno sensitive capability
  • get_cookiesno sensitive capability
  • get_htmlno sensitive capability
  • get_linksno sensitive capability
  • get_local_storageno sensitive capability
  • get_textno sensitive capability
  • get_titleno sensitive capability
  • go_backno sensitive capability
  • go_forwardno sensitive capability
  • hoverno sensitive capability
  • list_tabsno sensitive capability
  • mock_routeno sensitive capability
  • navigateno sensitive capability
  • new_tabno sensitive capability
  • pressno sensitive capability
  • recording_show_actionsno sensitive capability
  • reloadno sensitive capability
  • right_clickno sensitive capability
  • screenshotno sensitive capability
  • screenshot_elementno sensitive capability
  • scroll_pageno sensitive capability
  • scroll_tono sensitive capability
  • select_optionno sensitive capability
  • select_option_by_textno sensitive capability
  • set_browserno sensitive capability
  • set_cookieno sensitive capability
  • set_headlessno sensitive capability
  • set_local_storageno sensitive capability
  • set_viewportno sensitive capability
  • start_recordingno sensitive capability
  • stop_recordingno sensitive capability
  • switch_tabno sensitive capability
  • switch_to_frameno sensitive capability
  • switch_to_mainno sensitive capability
  • type_textno sensitive capability
  • uncheckno sensitive capability
  • wait_forno sensitive capability
  • wait_for_hiddenno sensitive capability
  • wait_for_responseno sensitive capability
  • wait_for_urlno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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
v2.1.0 latest A 96/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.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-playwright-tools/badge.svg)](https://mcptrustchecker.com/registry/mcp-playwright-tools)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-playwright-tools"><img src="https://mcptrustchecker.com/registry/mcp-playwright-tools/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-playwright-tools/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 mcp-playwright-tools --online --registry pypi

Use the free API → How scoring works

More in Developer Tools