android-renef-mcp
Related Servers
Alternatives to android-renef-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI agents to inspect APKs and resources, analyze native libraries, trace runtime behavior with Frida, and connect app screen actions to code through ADB.891MIT
- FlicenseAqualityFmaintenanceAn AI-driven Android dynamic analysis tool that enables AI models to perform automated reverse engineering by controlling Frida. It provides capabilities to inject scripts, manage application processes, and analyze real-time execution data through the Model Context Protocol.1070-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to see and control Android devices, with fast input, screenshots, UI element discovery, app and file management, shell access, and audio/video streaming or recording.468 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to inspect and control Android devices through ADB, including shell commands, logcat, UI automation, app management, screenshots, and file transfer, even inside Termux/proot without a native adb binary.41MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate Android devices or isolated Docker-based redroid environments over ADB, including installing and managing apps, navigating compressed UI hierarchies, performing gestures, capturing screenshots, and reading notifications. Provides token-efficient UI parsing and guardrails against SSRF, shell injection, and notification PII exposure.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Renef, providing dynamic instrumentation and reverse engineering capabilities for Android ARM64, including native hooking, Java interception, and memory manipulation.9MIT
TDQS
Scored across 38 tools
Most tools occupy clearly distinct niches: server lifecycle, session control, memory primitives, module inspection, hooking, and script/technique lookup are easy to separate, and descriptions explicitly flag the tricky pairs (mem_write vs mem_patch, module_exports vs module_symbols, list_hooks' native-only limitation). The main residual ambiguity is between overlapping memory-write/read helpers (mem_read vs mem_read_value vs mem_read_string, mem_write vs mem_patch), which are documented but still require the agent to read carefully. The exec/hook/watch family is well-differentiated.
Every tool carries the uniform `renef_` prefix and uses snake_case, so the set reads as one coherent namespace. Two ordering conventions coexist (resource_verb: mem_read, module_find, hook_native, technique_list vs verb_resource: list_apps, get_script, list_hooks), plus a bare noun (renef_sections), which is a minor deviation rather than a real inconsistency.
38 tools is well past the point where a single agent can hold the surface in working memory, and several are thin convenience wrappers (server_restart, mem_read_value, mem_read_string, module_find, backtrace) that arguably duplicate what renef_exec with inline Lua already provides. The domain is genuinely broad, but the surface could be consolidated substantially (e.g. a parameterized memory accessor instead of three read tools).
Lifecycle coverage is strong end-to-end: deploy/start/stop/logs, attach/spawn/resume/disconnect, memory scan/read/write/patch, module discovery, native and Java hooking, output capture, backtraces, and bundled script/technique libraries. Minor gaps remain — no thread enumeration, no register/context inspection, no Java class/method discovery tools (must be done via exec), and Java hooks cannot be listed or removed individually (documented as an upstream limitation).