No user-submitted related servers found.
Scored across 30 tools
Most tools have clearly distinct purposes, and the descriptions actively disambiguate the risky pairs (fill vs type, snapshot vs markdown vs extract vs evaluate, click target modes). The main residual overlap is among the several read/extract tools, where an agent must reason about which output format fits, but the guidance is explicit enough to make a correct choice.
All names are single lowercase words with no camelCase/snake_case mixing, which is readable and predictable in style. However, the set mixes action verbs (navigate, click, fill, evaluate) with bare nouns that bundle multiple operations (tabs, cookies, storage, memory, network, perf), so there is no single verb_noun convention to extrapolate from.
At 30 tools this is on the heavy side, and some consolidation is plausible (back/forward/reload could be one history tool; cookies/storage partially overlap, as do screenshot/pdf/snapshot). Still, the surface is a full browser automation stack with stealth, perf, network, and memory subsystems, so nearly every tool maps to a real capability rather than padding.
Coverage is broad: navigation, interaction, extraction, media capture, session persistence, diagnostics, stealth checks, and workflow memory are all present, so there are few dead ends. Gaps are minor but real — no dialog/alert handling, no iframe/frame-scoped operations, and no drag-and-drop or multi-select gesture support.