mcpbeat Sign in

Rogue Binary MCP Server

local only

Rogue Binary MCP runs on your own machine — the client starts it, so there is no endpoint to ping.

Rust MCP server for binary analysis and reverse engineering.

The linked repository no longer exists on GitHub — it was deleted or made private.

—
Installs / week
not published
—
Stars
on GitHub
—
Last commit
from GitHub
—
License
language unknown

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Alternatives to Rogue Binary MCP

same job, measured the same way
Reversecore MCP
by sjkim1127

Security-first MCP server for reverse engineering, malware analysis, forensics, and SAST.

166 installs/wk local only
JS Reverse MCP
by yuanhuakk

MCP server for JavaScript reverse engineering and browser debugging.

139 installs/wk local only
JS Reverse MCP
by yuanhuakk

MCP server for JavaScript reverse engineering and browser debugging.

local only
Super Trouper
by crissyfield

MCP server for the Frida reverse engineering toolkit.

171 installs/wk local only
Betterprompt MCP
by aungmyokyaw

MCP server for AI-enhanced prompt engineering and request conversion.

58 installs/wk local only
Reverse Engineer Anything (Docker)
by psyb0t

REA reverse-engineering MCP server in Docker, with JADX, Apktool and adb for APKs.

local only
X64dbg
by bromoket

MCP server for x64dbg debugger - 23 mega-tools for AI-powered reverse engineering and debugging

368 installs/wk local only
Code Fundi MCP
by felixwaweru

CodeFundi MCP server for codebase mapping and blast-radius analysis.

86 installs/wk local only

Rogue Binary MCP — questions

Answers built from our own checks of this server.

Why is there no uptime for Rogue Binary MCP?
Rogue Binary MCP runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone.
Is Rogue Binary MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.