← MCP server and skill grades

GhidraMCP

LaurieWired/GhidraMCP

B
Type
MCP server
Scanned
Nov 12, 2026
Version
1e980252087b
Files read
36

GhidraMCP connects AI coding agents to the Ghidra reverse-engineering tool so they can inspect binaries, decompile functions, and rename symbols or types. Its biggest risk is that the local HTTP server inside Ghidra has no password or token, allowing other local users or processes to read and modify the open project and allowing visited websites to trigger slow decompilations or probe function names via timing.

What it can reach

Network
Connects to and starts local loopback HTTP servers (127.0.0.1:8080 in the Ghidra plugin, a random loopback port in headless mode, and optionally 127.0.0.1:8081 when HTTP MCP transport is enabled).
Files
Reads the target binary, Ghidra installation, and extension JAR in headless mode, creates and optionally saves Ghidra project files, and reads or modifies symbol and type metadata in the open Ghidra program.
System
Starts an embedded Java Virtual Machine via PyGhidra in headless mode and invokes Ghidra's native decompiler process to analyze binaries.

Findings

2 medium2 low
  1. MediumGhidra loopback HTTP backend has no authentication

    extension/src/main/java/com/lauriewired/ghidramcp/http/BackendHttpServer.java:61

    When the GhidraMCP plugin is enabled in Ghidra (or when headless mode runs), it starts an HTTP server on 127.0.0.1 with no password or API token. Any other user account or unprivileged process on the same computer can query this port to read decompiled code, memory, strings, and file paths from the open binary, or overwrite function names, variable types, prototypes, and comments.

    Fix: Require a random shared secret token (for example in an Authorization header) on every request between ghidra-mcp and BackendHttpServer.

  2. MediumCross-origin browser GET requests bypass the Origin header check

    extension/src/main/java/com/lauriewired/ghidramcp/http/BackendHttpServer.java:162

    The Ghidra HTTP backend blocks browser requests by rejecting requests that include an Origin header. However, browsers omit the Origin header on cross-origin no-cors GET requests (such as image tags or no-cors fetch calls) while still sending Host: 127.0.0.1:8080. Unless blocked by browser local-network restrictions, any website the user visits while Ghidra is open can queue slow 60-second decompilations on the single-threaded backend and infer whether specific function names exist in the open binary by measuring response timing on /decompile.

    Fix: Reject requests where the Sec-Fetch-Site header is present and not none or same-origin, and require a custom authentication header so browsers must send a CORS preflight with an Origin header.

  3. LowOptional HTTP MCP transport has no authentication

    src/ghidra_mcp/server.py:37

    When started with --transport streamable-http or --transport sse, the Python MCP server exposes all Ghidra read and modification tools over HTTP (127.0.0.1:8081 by default) without authentication. Other local users or processes can call these tools directly, and anyone on the network can do so if --mcp-host is set to a non-loopback address.

    Fix: Add bearer-token authentication support for HTTP transports and refuse or warn strongly when binding --mcp-host to a non-loopback interface without authentication.

  4. LowInstallation examples run unpinned code from GitHub

    README.md:104

    The MCP client configuration examples instruct users to run uvx directly from git+https://github.com/LaurieWired/GhidraMCP without pinning a release tag or commit hash. If the repository were ever compromised, uvx could automatically fetch and run untrusted code when its cache refreshes.

    Fix: Pin the Git URL in all configuration examples to a specific release tag or full commit SHA.