Playwright MCP
Playwright MCP server
Is Playwright MCP safe? Strong public trust posture, backed by multiple independent signals.
Compare Playwright MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Playwright MCP scores 91.6/100 (Grade A), ranked #11 of 1371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.9/10; 100% of recent commits are signed; no published advisory affects its latest release (@playwright/mcp); last pushed 2026-10-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How Playwright MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 5.9 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, SAST 0 +4.5 → 96.1 A · #1 of 781
Chain of custody
Scanners check what the code says. This traces who ships Playwright MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Signed
github.com/microsoft/playwright-mcp, Apache-2.0, last pushed 2026-10-08. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.9/10 (scanned Oct 3, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies7
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 9CII-Best-Practices 0Code-Review 3Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 7SAST 0Security-Policy 10Signed-Releases -1Token-Permissions 0Vulnerabilities 0 -
Published packages Linked and attested
- npm @playwright/mcp Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: @playwright/mcp 0.0.83. No published advisory affects it (OSV, checked 2026-10-11).
Changes to this chain
- 2026-09-16 Package provenance attestation detected
- 2026-09-03 Package provenance attestation no longer detected
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Playwright MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Playwright MCP compares in MCP Servers
- #1 Mobile MCP 92.3 +0.7
- #2 Playwright MCP 91.6 this agent
- #3 Codebase Memory MCP 91.5 −0.1
- #4 SearXNG Search 89.3 −2.3
- #5 LinkedIn MCP Server 89.1 −2.5
Bars show each HVTrust score; the tick marks Playwright MCP’s 91.6.
Where the 91.6 comes from
HVTrust dimensions vs the MCP Servers average
91.6 / 100 · 100.0% confidencePlaywright MCP MCP Servers average (781 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
84.7 / 100Common questions about Playwright MCP
Does Playwright MCP publish package provenance?
Does Playwright MCP have an OpenSSF Scorecard?
Is Playwright MCP actively maintained?
What license does Playwright MCP use?
Are Playwright MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
Compare Playwright MCP head-to-head
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- browser
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Playwright MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Playwright MCP?
For maintainers
HVTrust scores Playwright MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/playwright-mcp)
<a href="https://hvtracker.net/agents/playwright-mcp"><img src="https://hvtracker.net/badge/playwright-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON