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.
| Evidence field | Ghidra MCP ServerMCP100 Selected | Windows-MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation github:bethington · Publisher source ↗ | Community implementation io.github.CursorTouch · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 14, 2026 Package: Not documented | Repo: Aug 14, 2026 Package: Aug 1, 2026 |
| Popularity evidence | ||
| GitHub stars | 3,308 GitHub stars · checked 2026-08-14T18:46:26.000Z | 6,749 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | No reliable download data | 40,449 PyPI Stats package downloads · checked 2026-08-14T18:46:26.000Z |
| External adoption evidence |
|
|
| 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 | 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. | Stdio has no network listener. Non-loopback HTTP requires an auth key or OAuth unless insecure access is explicitly allowed; IP allowlists, TLS, CORS, and host validation are documented. |
| Cost | The Apache-2.0 project lists no MCP fee. Ghidra, Java, Maven, hosting, and shared-server costs are separate. | The MIT-licensed project lists no MCP fee. Windows, Python, hosting, client, and model costs are separate. |
| Permissions | 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. | Runs with the invoking user's full Windows permissions, including PowerShell, files, registry, processes, UI input, screenshots, and web scraping; many actions are irreversible. |
| Data handling | 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. | Processing is local. Telemetry excludes screenshots, state captures, arguments, and outputs but includes status, duration, tool and client information, anonymized sessions, and possibly paths in error messages. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | 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. | It is not sandboxed and can delete files, alter registry or system settings, type into applications, and execute PowerShell. Use a VM or low-privilege account, backups, supervision, loopback binding, and disabled high-risk tools. |
| Evidence date | ||
| Editorial review | 2026-08-11 | 2026-08-11 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →