ReVa 7.3.1 builds for Ghidra 12.1.3 and runs on MCP SDK 2.0
3 hours ago
ReVa is the Ghidra extension that gives an AI model an MCP server for reverse engineering. Version 7.3.1 ships a build for Ghidra 12.1.3, and it moves ReVa onto version 2.0 of the MCP Java SDK. Here's what that changes for you, and what to check before you upgrade.
Ask about this presentation
Chapters
Show transcriptHide transcript
ReVa is the Ghidra extension that gives an AI model an MCP server for reverse engineering. Version 7.3.1 ships a build for Ghidra 12.1.3, and it moves ReVa onto version 2.0 of the MCP Java SDK. Here's what that changes for you, and what to check before you upgrade.
ReVa installs as one zip per Ghidra version, through Ghidra's extension manager. This release ships zips for Ghidra 12.0, 12.1, and the new 12.1.3. The patch builds for 12.0.1 through 12.0.4, which 7.3.0 shipped, are no longer in the build list.
Only one Java file outside the tests changed, and it's a fix for 12.1.3 support. The exporter class, which comes from the extension template, gains a method that says whether it can export a given type of Ghidra object. It returns false, so the exporter takes no object types.
The bigger change sits underneath the server. ReVa's build now pulls version 2.0.0 of the Model Context Protocol Java SDK, up from 1.1.3. That's the library that speaks MCP to your client, whether it's Claude Code, VS Code, or another one.
With SDK 2.0, each tool call is checked against the tool's input schema before ReVa's own handler runs. Pass an unknown correlator name to diff add correlator, and the error now names the correlator field, where it used to quote your value. Diff list functions now refuses a correlators argument, because its schema doesn't declare one. If you script these tools, send only the arguments each tool declares.
Libraries that ship inside the extension moved up as well. Jetty, the embedded web server, moves to 12.1.12, and Jackson to 2.22.1. Release files are still signed with Sigstore, now through version 3.5.0 of its GitHub action, and every zip comes with a matching Sigstore file to check it against.
In the Ghidra interface, download the 7.3.1 zip that matches your Ghidra version and install it with the extension manager. For headless use, the Python package is on PyPI as 7.3.1, and the readme installs it with uv tool install. One reason to wait. If you're on Ghidra 12.0.1 through 12.0.4, this release has no zip built for your version, so stay on 7.3.0 for now.
This release adds no new tools or settings. What you get is a Ghidra 12.1.3 build, version 2.0 of the MCP SDK underneath, and stricter checking of tool arguments. The release and its zips are on the reverse engineering assistant page on GitHub, from CyberKaida.







