You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`--http`| off | Serve over HTTP instead of stdio |
283
+
|`--host`|`127.0.0.1`| Bind address for `--http` mode |
284
+
|`--port`|`8651`| Port for `--http` mode |
285
+
|`--jadx-host`|`127.0.0.1`| Hostname/IP of the JADX AI MCP Plugin |
286
+
|`--jadx-port`|`8650`| Port of the JADX AI MCP Plugin |
287
+
288
+
**Docker / Remote VM example:**
289
+
```bash
290
+
uv run jadx_mcp_server.py --http --host 0.0.0.0 --port 8651
291
+
```
292
+
293
+
**JADX running on a different machine:**
294
+
```bash
295
+
uv run jadx_mcp_server.py --http --jadx-host 192.168.1.100 --jadx-port 8650
296
+
```
297
+
298
+
> [!CAUTION]
299
+
> ### ⚠️ Security Warning — Remote Binding
300
+
>
301
+
> When using `--host 0.0.0.0` (or any non-localhost address), the MCP server binds to **all network interfaces** over **plain HTTP with no authentication**. This means:
302
+
>
303
+
> -**Anyone on the network** can connect and invoke all MCP tools
304
+
> - There is **no TLS encryption** — traffic can be intercepted
305
+
> - An attacker can use the server to **read decompiled code**, **rename classes/methods**, and **access debug info**
306
+
>
307
+
> **Mitigations:**
308
+
> - Only bind to `0.0.0.0` on **trusted, isolated networks** (e.g., Docker bridge, local VM)
309
+
> - Use a **firewall** to restrict access to the MCP port
> Similarly, `--jadx-host` with a non-localhost address means the MCP server will make **unauthenticated HTTP requests** to that host. Ensure the target is trusted.
0 commit comments