No user-submitted related servers found.
Scored across 29 tools
Most tools have clear, distinct roles within browser QA: navigation, interaction, evidence capture, recording, and coverage. There is some overlap between click_what and test_action, and between verify_persistence and record_bug's verify path, but the descriptions generally make the intended choice clear.
All names use snake_case, but the naming conventions are mixed: verb-first tools like click_what and type_into, bare verbs like navigate and observe, and noun-first forms like capsule_save, coverage_update, and regression_check. The names remain readable, but the pattern is not predictable across the set.
With 29 tools, the surface is quite heavy for a single MCP server and exceeds typical well-scoped ranges. While the domain is broad, several low-level controls such as resize, scroll_down, go_back, and press_key could be consolidated into broader interaction tools.
The set covers the core exploratory testing lifecycle: session start/end, navigation, interactions, form submission, responsive emulation, screenshots, error capture, persistence checks, regression checks, coverage, and test export. Minor gaps such as forward history, drag-and-drop, or explicit multi-tab handling are not fatal for most workflows.
