No user-submitted related servers found.
Scored across 28 tools
Each tool targets a distinct resource or action, and near-overlapping pairs are explicitly disambiguated in their descriptions (parse_url vs. read_page, set_viewport vs. resize_window, get_cookies/get_storage vs. eval_js). An agent can reliably select the right tool without guessing.
All tool names share the zerodom_ prefix and snake_case convention, which makes them predictable. However, the verb style is mixed—get_/list_/read_/parse_/set_/click_/fill_—and a few noun-form names like zerodom_screenshot, zerodom_status, zerodom_network_log, and zerodom_hidden_fields break the otherwise action-first pattern.
28 tools is above the typical well-scoped range and makes the surface feel heavy, though the server covers a broad domain spanning browser automation, DOM interaction, tab management, network visibility, and security testing. It is not bloated to the point of being unusable, but the count is borderline.
The toolset covers the core browser-automation lifecycle well: navigation, page reading, interaction, tabs, state inspection, screenshots, network visibility, and identity-based replay. Minor gaps like explicit page reload/back/forward, cookie/storage mutation, or a dedicated wait-for-condition helper are workarounds rather than dead ends.