registry / record
@executeautomation/playwright-mcp-server
Does @executeautomation/playwright-mcp-server MCP work in Claude Code and Cursor? Throne executed @executeautomation/playwright-mcp-server mcp in a single-use Firecracker microVM and replayed both recorded client behaviours. Compatibility verdict: fit. Is @executeautomation/playwright-mcp-server mcp safe? Static security scan: 1 finding(s) to review under security ruleset v1. The full per-step results, security findings, scan date, and evidence hash are below.
> throne registry @executeautomation/playwright-mcp-server
sealed
- scan id
- 458684b9a4dd46bda7db6e13dbab0a14
- target
- @executeautomation/playwright-mcp-server
- sealed at
- 2026-06-16 17:36:10Z
- evidence hash
- sha256:9d5bc1e5c4bd57506238629a08f73306ac70b130a60983ba698c8fe86b736392
initialize ok: server playwright-mcp 1.0.11, negotiated protocolVersion 2025-11-25, capabilities ['resources', 'tools']
supported: tools/list (33 tools), resources/list (1); method not found (tolerated): prompts/list
all 33 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=serial): 0 ok, 4 returned tool-level errors (expected for synthesized args), 6 did not answer within 10s (tool may do heavy work)
structured error responses, connection survived, wrong_type_args: start_codegen_session:accepted (returned result); end_codegen_session:accepted (returned result); get_codegen_session:accepted (returned result); clear_codegen_session:accepted (returned result); playwright_navigate:no response (silent), connection alive; unknown_method: error(-32601); invalid_id: no response (silent), connection alive; oversized_input: accepted (returned result); recovery: accepted (returned result); cancellation: accepted (returned result); old_version: accepted old version 2024-10-07, negotiated 2024-10-07, server may have stale protocol handling
no streaming-capable tool declared by this server
read console://logs (1 content blocks); subscribe capability not declared
ladder 1 overlapping playwright_console_logs calls: max_observed_stable_concurrency=1; all ids answered exactly once at every level
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
initialize ok: server playwright-mcp 1.0.11, negotiated protocolVersion 2025-11-25, capabilities ['resources', 'tools'] [request_strategy=pipelined, connection_count=2, second connection established]
supported: tools/list (33 tools), resources/list (1); method not found (tolerated): prompts/list; notes: connection 2 confirms 33 tools
all 33 tool inputSchemas are valid JSON Schema
called 10 of 10 tools (cap 10, strategy=pipelined): 0 ok, 4 returned tool-level errors (expected for synthesized args), 6 did not answer within 10s (tool may do heavy work)
survived probes but no structured error response, handshake: probe handshake failed or died
no streaming-capable tool declared by this server
read console://logs (1 content blocks); subscribe capability not declared
ladder 1/2/4/6 overlapping playwright_console_logs calls: max_observed_stable_concurrency=6; all ids answered exactly once at every level
step timed out after 30s, threshold is assumed, not calibrated to real client behavior
"prepare" runs on git-dependency installs and local dev (not registry installs): 'npm run build'
package/package.json- target
- @executeautomation/playwright-mcp-server npm
- engine
- sandboxed
- claude code
- calibration: partial recorded=9,spec=0,assumed=9
- cursor
- calibration: partial recorded=11,spec=0,assumed=7
- chatgpt desktop
- calibration: unavailable recorded=0,spec=2,assumed=16
- steps exercised
- 14 of 18
- test suite
- v1.0.0
- security ruleset
- v1.0.0
- sealed at
- 2026-06-16 17:36:10Z
- evidence hash
- sha256:9d5bc1e5c4bd57506238629a08f73306ac70b130a60983ba698c8fe86b736392
- valid until
- 2026-09-14
paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.
[](https://usethrone.dev/server/executeautomation-playwright-mcp-server)maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.