e2e-verifier
Related Servers
Alternatives to e2e-verifier
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI clients to reproduce reported UI issues in an isolated, policy-restricted browser context, gather sanitized evidence, distinguish observed facts from candidate causes, and produce structured reports plus reviewable Playwright regression tests.7MIT
- AlicenseAqualityCmaintenanceGives AI agents a real Chromium browser via Playwright to QA-test web apps, with pass/fail assertions, network mocking, recorded traces and reports, and safety guards that block live payment traffic. Test outcomes come back as explained verdicts suitable for review or email delivery.18MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to verify application changes by running browser workflows, executing independent state assertions, and producing replayable evidence.3 npmMIT

ProdPoke MCP Serverofficial
AlicenseNot gradedqualityDmaintenanceEnables AI to perform real-browser QA testing on websites via Playwright, finding bugs, accessibility, SEO, and performance issues through natural language conversations.1MIT- AlicenseBqualityBmaintenanceEnables a connected model to inspect a live Chromium page, click and fill controls, and verify outcomes so single scenarios or full workflows can be checked for functional, visual and defensive QA issues. Findings — including screenshot evidence, severities and reproduction steps — are exported as JSON and Markdown bug reports for developers.18MIT

QualityMax QA MCPofficial
AlicenseAqualityBmaintenanceEnables coding agents to independently verify web changes by scanning pages, inspecting UI structure, generating Playwright reproductions, and executing tests with structured QA evidence.485 npm4MIT
TDQS
Scored across 18 tools
Tools are grouped into clear clusters: target probing, session control, schema/validation, ticket/scenario runs, and run artifacts. The only real ambiguity is discover_elements vs session_inspect, which perform nearly the same ARIA snapshot/target query and differ only by whether an interactive session is already open; probe_target and session_open also both open a URL but have different intent.
Most tools follow clear snake_case verb_noun names (validate_ticket, run_ticket, list_runs, delete_run), and the session_* prefix makes that cluster immediately recognizable. It is not completely uniform because session tools invert the order (session_open instead of open_session) and server_info is a noun_noun outlier, but the pattern is still predictable.
18 tools is on the heavier side, but each one maps to a distinct stage of the workflow: one-off probing, session lifecycle, ticket/scenario execution, and artifact retrieval. The count is slightly above the ideal range but feels justified by the domain rather than bloated.
The tool surface covers the full lifecycle: probe/open, inspect/discover targets, act/assert, annotate/screenshot, close session, run tickets/scenarios, fetch runs/artifacts, and delete. There are no obvious dead ends or missing operations for a bug-verification server.