Reversecore MCP
Security-first Model Context Protocol server for reverse engineering, malware analysis, digital forensics, vulnerability research, and SAST.
Reversecore MCP gives MCP-compatible AI agents structured access to Radare2, r2ghidra, YARA, LIEF, Capstone, angr, Qiling harness generation, Volatility3, Scapy, and additional analysis engines. It is designed around explicit workspace boundaries, input validation, non-root containers, and security regression testing.
Installation
Full container image — recommended
The container image includes the supported native toolchain and is the most reproducible installation method:
docker run -i --rm \
-v /absolute/path/to/samples:/app/workspace \
-e REVERSECORE_WORKSPACE=/app/workspace \
-e MCP_TRANSPORT=stdio \
ghcr.io/sjkim1127/reversecore_mcp:3.0.5
Python package
Install the MCP server and all supported Python feature extras from PyPI:
pip install "reversecore-mcp[full]"
Native programs such as Radare2, YARA, Graphviz, Binwalk, and The Sleuth Kit must be installed separately when using the Python package directly.
Qiling isolation: the server can generate Qiling/AFL harnesses, but Qiling is intentionally not installed by the
fullextra. Qiling 1.4.6 depends on a legacy Pillow line with known vulnerabilities. Execute generated harnesses only in a separate disposable sandbox; seedocs/EMULATION.mdin the repository.
Run the stdio server with:
MCP_TRANSPORT=stdio \
REVERSECORE_WORKSPACE=/absolute/path/to/samples \
reversecore-mcp
MCP client configuration
{
"mcpServers": {
"reversecore": {
"command": "reversecore-mcp",
"env": {
"MCP_TRANSPORT": "stdio",
"REVERSECORE_WORKSPACE": "/absolute/path/to/samples"
}
}
}
}
Capabilities
- Static analysis, disassembly, decompilation, cross-references, and CFG recovery
- Malware triage, IOC extraction, YARA scanning, and MITRE ATT&CK mapping
- Symbolic execution, emulation harness generation, fuzzing, and ROP analysis
- Memory, disk, network, and host-artifact forensics
- Python and C/C++ source-code security analysis
- Structured evidence, session tracking, metrics, and report generation
Security model
Reversecore MCP processes potentially hostile binaries. Use a dedicated workspace and prefer the hardened container configuration for untrusted samples. The project CI includes dependency auditing, CodeQL, secret scanning, container scanning, path-boundary tests, fuzzing, and network-isolation checks.
Detailed configuration, tool documentation, Docker Compose profiles, and client examples are available in the GitHub repository.
Registry identity
- MCP Registry name:
io.github.sjkim1127/reversecore-mcp - PyPI package:
reversecore-mcp - OCI image:
ghcr.io/sjkim1127/reversecore_mcp
License
MIT
Metadata
Release files for reversecore-mcp 3.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| reversecore_mcp-3.0.5.tar.gz | 485.4 kB | With provenance | Details for reversecore_mcp-3.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| reversecore_mcp-3.0.5-py3-none-any.whl | Python 3 | none | any | Details for reversecore_mcp-3.0.5-py3-none-any.whl |
Total release size: 1.0 MB
Release files / reversecore_mcp-3.0.5.tar.gz
| Download URL | reversecore_mcp-3.0.5.tar.gz |
|---|---|
| Size | 485.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62baccecd6e10d49a71dac31ac45b0a23e1209474c656b55a8ad4d015d0caee8
|
|
BLAKE2b-256 checksum How to use checksums |
aadb3a5500ef3669f096e3e18672f1346caecd34bf489562117bf30b00a2f2ae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency logRelease files / reversecore_mcp-3.0.5-py3-none-any.whl
| Download URL | reversecore_mcp-3.0.5-py3-none-any.whl |
|---|---|
| Size | 537.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07b72aa5bbc9463c453b23db91c59035e243f5a33296a9fc2602f37fc719f4ee
|
|
BLAKE2b-256 checksum How to use checksums |
2c0591a0ade197ed95f362988795b29b2a380a1625dc6e56193c41ba6f81f6ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency logSecurity for reversecore-mcp 3.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for reversecore_mcp-3.0.5.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.