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.
git clone --depth 1 https://github.com/daedalus/mcp_reverse_engineeringWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/daedalus/mcp_reverse_engineering/mcp_reverse_engineering)<a href="https://agentmods.dev/mcp/daedalus/mcp_reverse_engineering/mcp_reverse_engineering"><img src="https://agentmods.dev/badge/mcp/daedalus/mcp_reverse_engineering/mcp_reverse_engineering/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/daedalus/mcp_reverse_engineering/mcp_reverse_engineering"><img src="https://agentmods.dev/badge/mcp/daedalus/mcp_reverse_engineering/mcp_reverse_engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo ago.
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.
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.
What it actually says
{
"mcp_reverse_engineering": {
"command": "uvx",
"args": [
"mcp_reverse_engineering"
],
"env": {}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 9 lines scan A 2ae37ceedfa5
mcp_reverse_engineering is an MCP server published in the GitHub repository daedalus/mcp_reverse_engineering (1 stars, last pushed 5mo 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.
Other mcp servers, from other repositories
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.
rbinmcp
MCP server "rbinmcp" as configured in kirkderp/rbinmcp. Runs in Docker (ghcr.io/kirkderp/rbinmcp:1.3.0).
codecartographer
Turn an unfamiliar codebase into validated architecture, contracts, and a reimplementation spec. Runs locally from the codecartographer-pi npm package.
white-hat-agent
MCP server "white-hat-agent" as configured in kappa9999/white-hat-agent. Runs locally from the white-hat-agent Python package.
oe-mcp
OE MCP Server - connect Claude Code, Cursor & Windsurf to enterprise data sources. One binary, one JSON config. Runs locally from the @openenthrium/oe-mcp npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.