Related Servers

Many tools are exact or near-exact duplicates because v1.9.5 consolidated older tools into mode-based umbrella tools but left the old standalone tools registered (e.g., browser_errors vs browser_errors_aggregate, browser_flow mode=chain vs browser_chain, browser_visual vs browser_visual_compare, security_scan vs security_headers_check). Audit and check tools also heavily overlap (browser_full_audit, browser_smoke_test, browser_visual_check, browser_a11y_check, lighthouse_audit, validation_check). An agent cannot reliably select between deprecated and current variants.

The dominant pattern is readable snake_case with domain prefixes and verb_action names (browser_*, validation_*, security_*, skill_*), and mode-based umbrella tools mostly follow that convention. However, the pattern is diluted by bare noun tools (browser_artifacts, browser_state, evidence, contract), unprefixed outliers (api_probe, screenshot_diff, css_var_check, bypass_login), and deprecated standalone names that no longer match the consolidated naming scheme.

142 tools is an extreme count for any MCP server, and the list is inflated by deprecated aliases, standalone versions of merged tools, and multiple overlapping audit/check capabilities. This imposes a heavy selection and context burden on agents and should be reduced to a focused set of roughly 30-40 unique capabilities organized via mode parameters.

The server covers the verification domain remarkably broadly: browser lifecycle, interaction, assertion, error/network diagnostics, visual regression, performance, accessibility, security scanning, API contracts, evidence, trace correlation, session management, and MCP self-checks are all present. Minor gaps or workarounds exist (e.g., no standalone browser_assert tool, no direct storage clearing without browser_eval), but no major workflow dead end is apparent.