What is mcp_reverse_engineering?

A local, sandboxed connector that provides reverse-engineering tools through several integrations. It runs from a Python package using the MCP tool protocol.

Use it when an agent needs access to the reverse-engineering tools exposed by the mcp_reverse_engineering package.

It gives an agent a configured local entry point for reverse-engineering work without requiring manual tool setup for each integration.

mcp_reverse_engineering — MCP server by daedalus

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add mcp/daedalus/mcp_reverse_engineering/mcp_reverse_engineering

Clone the repo

git clone --depth 1 https://github.com/daedalus/mcp_reverse_engineering

Made for: Claude Code, Codex, Cursor.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod in the catalogue.

Security

Grade A, and why

mcp_reverse_engineering scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to mcp-reverse-engineering — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

server.json · 9 lines

What it actually says

{
  "mcp_reverse_engineering": {
    "command": "uvx",
    "args": [
      "mcp_reverse_engineering"
    ],
    "env": {}
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 9 lines scan A 2ae37ceedfa5

Subscribe to this mod's changes

mcp_reverse_engineering is an MCP server published in the GitHub repository daedalus/mcp_reverse_engineering (1 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 100% identical to mcp-reverse-engineering, differing in 4 lines, and is treated as a copy.

Languages binary hexdump mcp objdump radare2 reverse-engineering

reversecore-mcp

A security-first MCP server that empowers AI agents to perform automated reverse engineering, malware analysis, forensics, vulnerability research, and SAST — powered by Radare2, YARA, LIEF, Capstone, and more. Runs locally from the reversecore-mcp Python package.

sjkim1127/Reversecore_MCP · not measured

mcp_reverse_engineering

Getting it into your agent

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

reversecore-mcp

rbinmcp

arkana

codecartographer

mira

safe-android-reverser