<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ghidra on SoloSoft</title><link>https://www.solosoft.dev/tags/ghidra/</link><description>Recent content in Ghidra on SoloSoft</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.solosoft.dev/tags/ghidra/index.xml" rel="self" type="application/rss+xml"/><item><title>Auditing REA: 15,095 Stars, 133 MCP Tools, and the 209,619-Token Bill for Analysing Eight Files</title><link>https://www.solosoft.dev/post/rea-mcp-reverse-engineering-audit/</link><pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate><guid>https://www.solosoft.dev/post/rea-mcp-reverse-engineering-audit/</guid><description>&lt;p&gt;&amp;ldquo;See a feature you like. Understand how it works, down to the binary level.&amp;rdquo; That is REA&amp;rsquo;s pitch — one MCP server for reverse engineering across binaries, applications and runtime behaviour — and 15,095 stars on &lt;code&gt;morluto/rea&lt;/code&gt; say it landed. The repository is pushed to within an hour of my writing this, ships 26 npm versions in 88 days, and runs 16 GitHub Actions workflows with names like &lt;em&gt;Real Hopper E2E&lt;/em&gt; and &lt;em&gt;Real Ghidra Windows E2E&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;So I installed &lt;code&gt;rea-agents@5.0.0&lt;/code&gt;, spoke raw JSON-RPC to its MCP server, built an eight-file Electron application as a fixture, and pointed the analyser at a 14 MB JavaScript directory to find the edge. What came back is one of the more honest tools I have audited this year, and a bill nobody quotes in the README.&lt;/p&gt;</description></item></channel></rss>