dex-android-unpack
Related Servers
Alternatives to dex-android-unpack
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceEnables AI agents to inspect APKs and resources, analyze native libraries, trace runtime behavior with Frida, and connect app screen actions to code through ADB.89MIT
- AlicenseBqualityCmaintenanceEnables LLMs to query live decompiled Android app context through a JADX plugin, supporting class, method, and field inspection; source and smali retrieval; manifest parsing; vulnerability discovery; and reverse engineering.34Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with a unified MCP interface for Android APK reverse engineering, metadata analysis, Smali/resource editing, rebuilding, signing, verification, and ADB device testing.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to control Android devices through the Android Debug Bridge, covering device listing, shell commands, app install/uninstall, logcat reading, screenshots, UI automation (tap/swipe/type/key events), dumpsys queries, file transfer, port forwarding, permission management, and Wi-Fi pairing. Failures are mapped to typed, actionable causes and tool calls are safety-annotated and guardrailed, with multi-device calls scoped explicitly by serial.35454 npmMIT
- AlicenseBqualityBmaintenanceEnables control of Android devices via ADB for automation and testing. Supports app management, screen capture, UI analysis, and input simulation through natural language commands.9167 npm38MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to locally inspect Android APKs over MCP by decompiling Java, decoding resources, searching classes and methods, tracing references, and producing evidence reports with limitations.4MIT
TDQS
Scored across 13 tools
Each tool has a distinct, clearly bounded purpose: device/package listing, packer detection, APK pulling, and three separate unpacking pipelines (static, root-frida, no-root BlackDex) plus smali analysis. The prepare/action pairs (frida_prepare/frida_unpack, blackdex_prepare/blackdex_pull) are explicitly differentiated and cannot be easily confused.
Mostly consistent snake_case verb_noun with descriptive prefixes (frida_*, blackdex_*, smali_*). Minor deviation: some tools prefix the domain (smali_list_classes) while others use the plain action (list_packages, list_devices), and dex_to_smali mixes a to_ connector, but the pattern remains readable and predictable.
13 tools is well within the ideal range and each tool earns its place by covering a distinct workflow step. No redundant or filler tools; the count precisely matches the multi-method unpacking domain.
Strong lifecycle coverage: enumerate devices/packages, detect packers, pull APKs, run all three unpacking methods, and analyze results via smali listing/reading/searching. Minor gaps exist (e.g. no Java decompilation or output cleanup), but core end-to-end workflows are fully covered.