No user-submitted related servers found.
Scored across 20 tools
Most tools target distinct resources (dex, native, frida, webview, resources, script), and several descriptions explicitly disambiguate neighbors (search is not DEX xref, native vs frida static/dynamic). However the `artifact` (content-based identification/extraction) vs `artifacts` (list/read task files) pair is a near-collision that will cause misselection, and `apk`/`packages`/`decode` plus `framework`/`managed` have overlapping edges that only the long descriptions disentangle.
Naming is consistently lowercase single tokens throughout, which is readable, but it never encodes an action (no verb_noun pattern) so the operation must be inferred from the description. Singular/plural collisions (`artifact` vs `artifacts`) and role-mixed tokens (`doctor`, `guidance`, `jobs`) weaken predictability.
20 tools is at the heavy end, though the domain genuinely spans static analysis, native, .NET, dynamic instrumentation, WebView, devices, rebuild, and job/artifact management. Each tool roughly maps to a real capability, but the set is large enough that a few (guidance, doctor, jobs, artifacts) could plausibly be folded together.
Coverage is broad: inspect/decode APK, DEX and resource queries, native and managed analysis, Frida tracing, WebView debugging, rebuild/sign, search, evidence, and job orchestration form a coherent workflow. Minor gaps exist — device interaction stops at getprop/packages/processes/logcat with no file push/pull or device-side artifact retrieval, and keystore creation is assumed rather than provided.