Android dynamic analysis MCP server: adb, Frida, mitmproxy, apktool, jadx
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mobile-re-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# mobile-re-mcp (Python) The live-device half of [mobile-re-mcp](https://github.com/FlyPhantomFly/mobile-re-mcp). It is an MCP server that lets an AI assistant drive adb, Frida, mitmproxy, apktool and jadx against a test phone: decompile an app, hook it, read its traffic, patch it, sign it and install it again. The npm package with the same name only reads APK and IPA files and never runs anything. It is the better first step, and this one is for when you need the app running. Android only. ## Install ```bash pip install "mobile-re-mcp[all]" mobile-re-mcp-py --setup ``` It needs Python 3.11 or newer. The base install is just the MCP server. The `[all]` extra adds Frida, androguard, apkid, apkleaks, mitmproxy and quark-engine, and you can pick parts instead: `frida`, `static`, `network`, `analysis`. If Frida is already pinned in your environment, install without extras and the server will not touch it. `--setup` downloads pinned, checksum-verified copies of apktool, jadx, uber-apk-signer and Il2CppDumper into `~/tools`. adb comes from your package manager (`sudo apt install adb`). The command is `mobile-re-mcp-py`, so it does not clash with the npm package's `mobile-re-mcp`. ## Connect it Claude Code: ```bash claude mcp add mobile-re-py -- mobile-re-mcp-py ``` opencode, in `~/.config/opencode/opencode.json`: ```json { "mcp": { "mobile-re-py": { "type": "local", "command": ["/path/to/venv/bin/mobile-re-mcp-py"], "enabled": true } } } ``` Use the full path to the command if it lives in a virtualenv. Any other client needs only the command, with no arguments. Start with a check of what is installed. Ask "Run check_tools", and the assistant lists which tools it found and which are missing. ## A first session Ask in plain language and the assistant picks the tools. Some prompts and what they use: - "List my devices, then push frida-server to the phone and start it." (`adb_devices`, `frida_server_push`) - "Decompile /home/me/apks/app.apk and search the strings …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.