re-audit-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@re-audit-mcprun a full audit on ./my_app.apk and summarize the findings"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
re-audit
Static, reverse-engineering-assisted vulnerability triage, as a CLI and an MCP server so an AI agent (Claude Code, etc.) can drive it.
It extracts strings, flags hardcoded-secret patterns, checks ELF/PE/Mach-O
exploit mitigations, and audits Android APK manifests -- then hands back a
single structured report with a summary_findings list.


Everything shown above is real output from this repo's own code, run
against notepad.exe and the synthetic secrets fixture in tests/ --
nothing in these assets is staged or fabricated.
Scope -- read this first
This tool is static-analysis only:
It never sends a network request.
It never executes, launches, or instruments the target.
It only reads bytes from a local file you point it at.
That makes it safe to run on anything sitting on your disk. It does not make it legal to run against a service you don't own or aren't authorized to test. Before pointing this at anything:
Your own code/builds -- always fine.
CTF binaries, crackmes, deliberately vulnerable apps (Juice Shop, DVWA, HackTheBox/picoCTF targets) -- fine.
A real company's app or website -- only if you have a signed authorization, or the target has a published bug-bounty / vulnerability disclosure program (HackerOne, Bugcrowd, or the vendor's own
security.txt/ bounty page) and your activity stays inside its stated scope and rules.If no scope or program exists, don't test it. Report findings only through the vendor's official security contact, or via a national CERT (e.g. KISA in Korea) if there's no direct channel. Never demand payment for a report you weren't invited to submit -- that can be read as extortion.
Findings this tool produces are heuristic candidates for human review, not confirmed, exploitable vulnerabilities. Always verify manually before reporting anything to a vendor.
Related MCP server: apk-docforge
Install
pip install -e .CLI usage
re-audit scan ./my_app.apk # full audit, human-readable
re-audit scan ./my_app.apk --json # full report as JSON
re-audit scan ./binary.exe --out report.json
re-audit scan ./binary.exe --html report.html # styled, shareable HTML report
re-audit strings ./binary.exe # just string extraction
re-audit secrets ./binary.exe # just secret-pattern scanning
re-audit binary ./binary.exe # just exploit-mitigation checks
re-audit apk ./my_app.apk # just APK manifest auditMCP server usage
Run directly:
re-audit-mcpOr register it with Claude Code (claude mcp add) / your MCP client's
config, pointing it at re-audit-mcp (stdio transport). Exposed tools:
Tool | Purpose |
| Identify ELF / PE / Mach-O / APK / JAR by magic bytes |
| Extract + classify strings (URLs, IPs, paths, risky API names) |
| Hardcoded credential/token/key pattern + high-entropy scan (redacted) |
| NX, PIE/ASLR, RELRO, stack canary, CFG, risky imports |
| Debuggable/backup/cleartext flags, dangerous permissions, exported components |
| Runs all of the above and merges into one report |
The server's instructions tell the connected agent to confirm the target is in-scope before scanning and to present findings as unverified candidates -- but that's a prompt-level nudge, not an enforcement mechanism. The scope decision is still yours.
What it checks
Strings: URLs, IPs, filesystem paths, references to risky functions (
strcpy,system,eval(,pickle.loads, etc.)Secrets: AWS/Google/Slack/GitHub key formats, PEM private key blocks, JWTs, generic password/API-key assignments, DB connection strings, plus high-entropy token detection for anything the regexes miss.
Binaries (via LIEF): NX/DEP, PIE/ASLR, RELRO (ELF), stack canary, Control Flow Guard / SafeSEH (PE), Authenticode signature, and a curated list of memory-unsafe imports.
APKs (via androguard):
debuggable,allowBackup,usesCleartextTraffic, dangerous permissions, and exported activities/services/receivers/providers withoutexported="false".
Development
pip install -e .
pip install pytest
pytest tests/ -vTests run against real artifacts (C:\Windows\System32\notepad.exe) rather
than mocks, so CI runs on windows-latest. The APK analyzer's end-to-end
test needs a real debug .apk you own -- point RE_AUDIT_TEST_APK at one
locally to run it; it's skipped otherwise (no binary fixtures are committed
to keep the repo small).
To regenerate examples/demo.gif: python scripts/make_demo_gif.py (pure
Pillow, hand-renders the terminal frames -- no pty/ffmpeg dependency).
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Compliance & security scan for your app: secrets, exposed files, headers, privacy, AI-disclosure.
Security scanner for AI agents: prompt injection, leaked secrets, PII, and SSRF-risk URL detection.
30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform autonomous Android security analysis, including static analysis, dynamic analysis, and Frida instrumentation, powered by MobSF.4MIT
- FlicenseBqualityCmaintenanceEnables local-first static and optional controlled dynamic analysis of Android APK artifacts, with provenance-aware downloads, Markdown reports, and structured security findings via MCP stdio tools.9-
- FlicenseNot gradedqualityBmaintenanceEnables Android APK security auditing through natural language by decompiling APKs with Apktool and running static analysis heuristics for attack surface, permissions, secrets, crypto, native libraries, and more, with every analysis logged to disk as markdown reports.-
- AlicenseBqualityCmaintenanceEnables automated Android APK analysis by orchestrating seven specialist reverse-engineering agents in parallel, consolidating results into a unified report.7MIT