No user-submitted related servers found.
Scored across 14 tools
Most tools have clearly distinct purposes, but scan_codebase, get_coverage, and suggest_tests all return coverage gaps and test suggestions, creating real selection ambiguity. The descriptions clarify prerequisites somewhat, but an agent could still reasonably call the wrong one.
The majority of tools follow a clear imperative verb_noun snake_case pattern like scan_codebase, execute_scenario, and generate_report. However, login, cleanup, and configure are bare verbs, and run_converge uses a verb where a noun object would be more consistent with run_full_test.
Fourteen tools is within a reasonable range for a comprehensive testing workflow and most map to distinct phases. It feels slightly heavy because several tools overlap around coverage/suggestions and there is an all-in-one orchestrator, but no tool feels entirely superfluous.
The core web-testing lifecycle is well covered: configuration, login, codebase scanning, element discovery, scenario execution, coverage analysis, reporting, and cleanup. Minor gaps include no explicit way to retrieve past test results outside of generated reports or to abort a long-running convergence run.