No user-submitted related servers found.
Scored across 82 tools
Multiple tools have overlapping boundaries, especially around verification and evidence collection: verify.assert_screen_contains_text and verify.assert_navigation_reached both assert page-source text, while appium.observe_screen, verify.collect_evidence, and device.capture_screenshot all capture screen/evidence data. The many tap variants and several record/report/generate tools also make misselection likely without very careful description reading.
Tool names largely follow a consistent snake_case verb-first pattern with namespace prefixes, such as list_devices, build_debug_apk, and assert_visible. Minor deviations like code.git_diff and env.compatibility_matrix are noun-phrase names, and verbs like write/create/run are used somewhat interchangeably, but the overall convention is recognizable.
At 82 tools, the surface is extremely overgrown regardless of the server's broad mobile validation scope. Even accounting for Android, iOS, Appium, build, verification, flow memory, security, and CI, the count far exceeds what an agent can navigate efficiently. Many tools could be consolidated or exposed as parameterized subcommands.
The tool set covers the core mobile validation lifecycle well: build, install, launch, automate via Appium, verify, collect evidence, record flows, run security gates, and report to CI. Minor gaps exist, such as no direct Android app launch/stop utility, no iOS uninstall or clear-data operation, and limited Appium gesture coverage beyond coordinate swipes.