Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.hubertgajewski/playwright-report-mcp

NPM · PLAYWRIGHT-REPORT-MCP

Run Playwright tests and surface structured results for AI agents doing test failure analysis.

0 this week 94 Trust /100

Last scanned (1 hour ago)

Scores higher than 97% of npm servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to hubertgajewski/playwright-report-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 40 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 763 tokens (~152/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
    • Package version: 3.2.2 → 3.4.0 functional
  • 22 Oct 26 0
    • Stability: pass → 0.97 functional
  • 19 Oct 26 0
    • Package version: 3.2.2 → 3.4.0 functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/playwright-report-mcp@3.4.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo hubertgajewski/playwright-report-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/hubertgajewski/playwright-report-mcp/.github/workflows/release.yml@refs/tags/v3.4.0
Rekor log index 2955036629
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:002949e292e222c4af7274919cf392975b2859c27a2a99c6c1a7e10ed2666c8ba3613ffc9902d481c2bc58dce9bbbfd6281da4f8edba4b1784ea6dd64

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~763 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_failed_tests ~57

Return failed tests from the last run with error messages and attachment paths.

NameTypeReqDescription
workingDirectorystring–Playwright project directory. Absolute or relative to the MCP server launch directory. Defaults to ".". Must be under PW_ALLOWED_DIRS.

No output schema declared.

No examples provided.

get_run_status ~142

Return status for a tracked Playwright run. Pass runId for a specific background run, or omit it to inspect the latest tracked run for a workingDirectory. If no tracked run exists, returns idle with current results.json metadata; it does not inspect unrelated OS processes.

NameTypeReqDescription
runIdstring–Run identifier returned by run_tests with wait=false.
workingDirectorystring–Playwright project directory. Absolute or relative to the MCP server launch directory. Defaults to ".". Must be under PW_ALLOWED_DIRS. Used to find the latest tracked run when runId is omitted; when…

No output schema declared.

No examples provided.

get_test_attachment ~95

Read the content of a named attachment for a specific test from the last run.

NameTypeReqDescription
attachmentNamestringyesAttachment name, e.g. "AI diagnosis", "DOM"
testTitlestringyesExact test title as shown in the report
workingDirectorystring–Playwright project directory. Absolute or relative to the MCP server launch directory. Defaults to ".". Must be under PW_ALLOWED_DIRS.

No output schema declared.

No examples provided.

list_tests ~128

List all tests with their spec file and tags without running them.

NameTypeReqDescription
envobject–Environment variable overrides for the Playwright child process. Each key must be listed in PW_ALLOWED_ENV. Dangerous names (NODE_*, NPM_CONFIG_*, PATH, proxies, secrets) are always rejected. Values…
tagstring–Filter by tag, e.g. @smoke
workingDirectorystring–Playwright project directory. Absolute or relative to the MCP server launch directory. Defaults to ".". Must be under PW_ALLOWED_DIRS.

No output schema declared.

No examples provided.

run_tests ~341

Run Playwright tests and return structured results.

NameTypeReqDescription
browserstring––
envobject–Environment variable overrides for the Playwright child process. Each key must be listed in PW_ALLOWED_ENV. Dangerous names (NODE_*, NPM_CONFIG_*, PATH, proxies, secrets) are always rejected. Values…
headedboolean–Run with a visible browser window. Omitting or setting false leaves playwright.config.ts intact — Playwright has no --no-headed flag, so false does not force headless when the config sets headed.
maxFailuresinteger–Stop the run after this many failures.
retriesinteger–Maximum retry count for flaky tests; 0 disables retries.
specstring–Spec file path, e.g. tests/navigation.spec.ts
tagstring–Tag filter, e.g. @smoke or @regression
timeoutinteger–Timeout in milliseconds for the whole test run. Defaults to 300000.
tracestring–Force Playwright tracing mode, overriding playwright.config.ts.
updateSnapshotsstring–Update snapshot baselines. Playwright default is "missing"; "changed" updates differing + missing.
waitboolean–Wait for completion before returning. Defaults to true. Set false to start a background run and poll it with get_run_status.
workersinteger–Number of parallel workers (positive integer).
workingDirectorystring–Playwright project directory. Absolute or relative to the MCP server launch directory. Defaults to ".". Must be under PW_ALLOWED_DIRS.

No output schema declared.

No examples provided.

Install

How do I install the io.github.hubertgajewski/playwright-report-mcp server?

io.github.hubertgajewski/playwright-report-mcp runs locally as an npm package, launched with npx -y playwright-report-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · playwright-report-mcp

# add to Claude Code
claude mcp add hubertgajewski-playwright-report-mcp -- npx -y playwright-report-mcp
Common questions

What is the io.github.hubertgajewski/playwright-report-mcp server?

io.github.hubertgajewski/playwright-report-mcp is listed in the public MCP registry as io.github.hubertgajewski/playwright-report-mcp. Run Playwright tests and surface structured results for AI agents doing test failure analysis. This page covers its npm package (playwright-report-mcp).

Is the io.github.hubertgajewski/playwright-report-mcp server safe to use?

io.github.hubertgajewski/playwright-report-mcp scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.hubertgajewski/playwright-report-mcp server expose?

io.github.hubertgajewski/playwright-report-mcp exposes 5 tools: run_tests, get_run_status, get_failed_tests, get_test_attachment, list_tests. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.

Is the io.github.hubertgajewski/playwright-report-mcp server still maintained?

io.github.hubertgajewski/playwright-report-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.hubertgajewski/playwright-report-mcp server under?

io.github.hubertgajewski/playwright-report-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.