Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

JADX-AI-MCP (Part of Zin MCP Suite)Ghidra MCP Server

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Chrome DevTools MCPMCP100 RecommendedoktaMCP100 RecommendedMCP Unity Editor (Game Engine)MCP100 RecommendedApify MCP ServerMCP100 RecommendedWindows-MCPMCP100 RecommendedIDA Pro MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	JADX-AI-MCP (Part of Zin MCP Suite)MCP100 Recommended	Ghidra MCP ServerMCP100 Recommended
Task fit
Best for	Navigating JADX decompilation, searching APK code, and accelerating reverse-engineering or security-analysis hypotheses	Querying decompilation, symbols, references, functions, and analysis state inside Ghidra
Not ideal for	Definitive vulnerability certification, dynamic analysis, or reviewing applications without authorization	Static analysis workflows that do not use Ghidra or do not need agent-driven interaction
Avoid when	APK contents, decompiled code, or findings cannot be shared with the connected AI client	The analyzed binary or Ghidra project cannot be exposed to the connected AI client
Provenance
Provenance details	Community implementation github:zinja-coder · Publisher source ↗	Community implementation github:bethington · Publisher source ↗
Maintenance
Maintenance details	Repo: Sep 23, 2026 Package: Not documented	Repo: Sep 22, 2026 Package: Not documented
Popularity evidence
GitHub stars	2,822 GitHub stars · checked 2026-09-24T04:14:47.694000Z	3,971 GitHub stars · checked 2026-09-24T04:14:26.335000Z
Client coverage
Client coverage details	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	The documented default is stdio with the HTTP endpoints on 127.0.0.1. The publisher explicitly warns that binding the MCP server to 0.0.0.0 or another non-localhost address exposes plain HTTP with no authentication or TLS, allowing anyone on that network to invoke all tools.	HTTP bearer authentication is optional through GHIDRA_MCP_AUTH_TOKEN; without it authentication is disabled. Non-loopback binding is refused without a token. Scripts require GHIDRA_MCP_ALLOW_SCRIPTS.
Cost	The publisher distributes the project under the Apache License 2.0 and lists no MCP server usage fee. JADX, local compute, the selected MCP client, and model-provider costs can still apply.	The Apache-2.0 project lists no MCP fee. Ghidra, Java, Maven, hosting, and shared-server costs are separate.
Permissions	The published tools can read decompiled code for classes and methods, smali, AndroidManifest.xml, string and resource files, cross-references, and debugger frames, threads, and variables from the project open in JADX. They can also rename classes, methods, fields, packages, and variables within the JADX analysis workspace.	Reads and writes binaries and projects, renames and types symbols, adds comments and structures, executes scripts, performs P-code emulation and debugging, and integrates with Ghidra Server.
Data handling	The publisher's architecture sends tool requests from the LLM client through the Python MCP server over HTTP to the JADX-GUI plugin, then returns source, resource, manifest, and debugger data to the connected client. The reviewed README does not document telemetry, retention, or model-training use, so those behaviors remain unknown.	Operates on local binaries and projects and optionally shared Ghidra Server data; decompilation, memory, debugger, and script results are returned through MCP. Telemetry and retention are not documented.
Limitations
Tradeoffs	JADX integration speeds static exploration, but decompilation is imperfect and AI-generated security conclusions can contain false positives or miss runtime behavior.	It accelerates navigation and analysis, but agent actions can alter project state and reverse-engineering output still requires expert validation.
Risk context	This server exposes sensitive reverse-engineering material and mutation tools for the APK project open in JADX. Keep both connections on 127.0.0.1 and prefer stdio; if remote access is unavoidable, use a trusted isolated network plus firewall or SSH tunnel. Treat decompiled source, resources, manifests, and debugger values as potentially confidential, and review rename operations before saving or exporting analysis artifacts.	Write access, optional arbitrary Java scripts, debugger control, and shared-server access create substantial integrity and confidentiality risk. Prefer loopback, bearer auth, scopes, scripts disabled, and supervised writes.
Evidence date
Editorial review	2026-08-11	2026-08-11
Candidate evidence	2026-09-24T04:25:05.554391Z	2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →