Reverso
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Reverso: Native reverse engineering toolkit
English | Bahasa Indonesia
Use Reverso only on files, applications and websites you are authorized to analyze.
Table of Contents
Related MCP server: Reverence
About
Reverso is a native-first reverse engineering toolkit for developers, security researchers and agentic tooling. It triages unknown binaries, inventories JavaScript bundles, and mirrors websites for offline analysis, from one command or one MCP server. Everything runs locally: no Ghidra, Hopper, IDA, Python or license server is required for the built-in analyzers, and the package ships with zero runtime dependencies.
"Analyze anything, install nothing."
Features
Analysis engines
Feature | Description |
Full triage report |
|
Format detection | Magic-byte detection for ELF, PE, Mach-O, ZIP (APK/IPA/JAR), WASM, DEX, PDF, PCAP and more |
Binary layout | ELF, PE and Mach-O structure: sections, program headers, imports, exports |
Hardening checks | PIE, NX stack, stack canary, RELRO and FORTIFY for ELF; ASLR, NX compat, Control Flow Guard, high entropy VA and Authenticode for PE |
Entropy analysis | Shannon entropy with high-entropy region detection for packed or encrypted content |
String intelligence | ASCII and UTF-16LE strings, categorized as URLs, IPv4, emails, paths, JWTs, AWS keys, GitHub tokens, Slack tokens, Google API keys, private keys and assigned secrets |
JavaScript analysis | Minification detection, obfuscation score with indicators, framework fingerprints (webpack, React, Vue, Angular, Next.js, Vite, Svelte, jQuery), source map reference, URL and API endpoint extraction, secret scanning |
Archive inventory | ZIP/APK/IPA/JAR entry listing with sizes, compression method, encryption flags, type detection and suspicious entry flagging |
Packer signals | UPX signature and stub detection, plus multi-region high entropy heuristic |
Website mirror
Feature | Description |
Same-origin mirroring |
|
Safety guard | Blocks loopback, private, link-local and reserved addresses (literal IPs and DNS answers) unless |
Resource caps | Limits pages, depth, file size and total bytes; skips cross-origin redirects |
Automation
Feature | Description |
MCP server |
|
Script-friendly | JSON output by default, Markdown reports with |
Environment self-check |
|
Requirements
Dependency | Minimum Version | Notes |
Node.js |
| ESM, TypeScript strict, zero runtime dependencies |
No C/C++ toolchain, Python, Java or external analysis tools are needed.
You can run the CLI straight from the repository without installing it globally. SeeInstallation, Option B.
Never used a terminal? Start here
Windows: press
Win + R, typewtorpowershell, press Enter.macOS: press
Cmd + Space, typeTerminal, press Enter.Linux: press
Ctrl + Alt + T, or findTerminalin your application menu.
Installation
Option A: Global command (npm link)
Install Git and Node.js (see the details below for Git).
Clone, build and link:
git clone https://github.com/nekonaru/reverso.git cd reverso npm ci npm run build npm linkIMPORTANTnpm run buildmust finish without errors. If it prints type errors, stop and open an issue instead of running the binary.Verify:
reverso doctor
Skip the Git step above. git --version should print a version.
Download the source archive from
GitHub, unzip
it, then run npm ci, npm run build and npm link inside the extracted
folder.
Option B: Run from the repository without installing
git clone https://github.com/nekonaru/reverso.git
cd reverso
npm ci
npm run build
node dist/cli.js doctorUse node dist/cli.js <command> anywhere you would use reverso <command>.
Usage
First launch
Check the runtime:
reverso doctorAnalyze a file:
reverso analyze ./some-file.binPoint your MCP client at
reverso mcp(see below)
Reverso is static-only. It never executes the file you analyze.
Everyday use
reverso analyze ./target.binfor a full triage report (add--format md --out report.mdfor Markdown)reverso format ./mystery.binto identify a filereverso layout ./target.elfandreverso hardening ./win32.exefor binary structure and protectionsreverso strings ./firmware.bin --min-length 6for categorized stringsreverso js ./app.min.jsto inventory endpoints and secrets in a web bundlereverso site https://example.com --out ./mirrorto mirror a site offlinereverso capabilitiesto list every analyzer and MCP tool
Use Reverso from an MCP client
reverso mcp speaks Model Context Protocol over stdio (protocol 2025-06-18).
Add it to your client configuration:
{
"mcpServers": {
"reverso": {
"command": "reverso",
"args": ["mcp"]
}
}
}Tools exposed: reverso_analyze, reverso_strings, reverso_entropy,
reverso_format, reverso_layout, reverso_hardening, reverso_archive_list
and reverso_js_analyze.
Project Structure
reverso/
├── src/
│ ├── core/ # format detection, entropy, hashes, strings, orchestrator, report
│ ├── binary/ # ELF / PE / Mach-O parsers and hardening checks
│ ├── archive/ # ZIP-family parser (APK/IPA/JAR detection)
│ ├── js/ # JavaScript bundle analysis
│ ├── web/ # website mirror (same origin, private-address guard)
│ ├── mcp/ # MCP stdio server
│ ├── doctor.ts # environment self-check
│ ├── index.ts # public API
│ └── cli.ts # command dispatcher (thin layer over the engines)
├── tests/ # unit and integration tests (vitest)
├── docs/
│ ├── specs/ # testable specification (done criteria)
│ └── brand.md # logo usage and colors
├── assets/logo/ # final logo files (mark, lockups, icons)
├── scripts/verify.mjs# local verification pipeline
├── README.md # this file (English)
└── README.id.md # Bahasa IndonesiaDevelopment
Add a new analyzer
Write the analyzer in
src/(pure functions, no I/O where avoidable).Register it in
src/core/analyze.tsand expose it fromsrc/index.ts.Add a CLI command in
src/cli.tsand an MCP tool insrc/mcp/server.ts.Add tests in
tests/and runnode scripts/verify.mjs.Document the command in both READMEs and the spec in
docs/specs/.
Run the verification pipeline
node scripts/verify.mjs(typecheck, tests with coverage, build, audit).Everything must pass before a pull request is opened.
CI runs the same pipeline on Ubuntu and Windows, Node 22 and 24.
Cut a release
Bump the version in
package.json(and the CLI banner constant) asMAJOR.MINOR.PATCH.Update
CHANGELOG.mdandCHANGELOG.id.mdwith the same sections as the release notes.Open a pull request; merge once CI is green.
Tag
vX.Y.Zon the merge commit and push the tag.Publish the GitHub Release with bilingual notes (
Project vX.Y.Zas the title).
dist/ is generated by npm run build. Never edit files in dist/ by hand
and never commit them.
Testing
npm ci
npm test # test suite
npm run test:coverage # tests with coverage thresholds
node scripts/verify.mjs # full pipeline (typecheck, coverage, build, audit)Check | Requirement |
Unit and integration tests | All pass (84 tests) |
Line coverage | At least 70% |
Branch coverage | At least 60% |
Type check |
|
Dependency audit |
|
Secret scan | gitleaks job in CI, zero findings |
Linting is the TypeScript compiler in strict mode (strict,
noUncheckedIndexedAccess, exactOptionalPropertyTypes). There is no separate
linter configuration by design.
Security
Reverso parses untrusted files without executing them, caps input sizes (256 MiB files, 64 MiB over MCP) and blocks private network addresses in its web mirror by default. The package has no runtime dependencies. Production dependencies are audited in CI on every push, and all CI runs include a secret scan.
Found a vulnerability? Use the repository's private vulnerability reporting on GitHub (Security tab, "Report a vulnerability"). Do not open a public issue for security reports.
Continuous Integration
Workflow | Purpose |
| Verify job (typecheck, tests with coverage, build, audit) on Ubuntu and Windows, Node 22 and 24, plus a gitleaks secret scan |
Branch protection on main requires every one of these checks to pass before
merging. Releases are cut only from green main after the security gate.
FAQ
No. All analysis is static. Nothing is loaded, run or emulated.
No. Reverso triages, inventories and scores. For decompilation, feed the file to a dedicated decompiler; use Reverso for triage, extraction and reporting.
No for analysis. The test suite and the mirror integration tests bind to loopback only during development. Analysis itself never touches the network.
High entropy (above roughly 7 bits per byte) usually means compressed, encrypted or packed content. Check the reported regions and the packer signals before assuming malware.
Not yet. Install from source as shown in Installation. The package manifest is release-ready; publishing is pending the first stable release.
Reverso is an independent project rebuilt from a study of publicly available tooling. No source code from other projects is included. It complements heavy interactive tools rather than replacing them.
Author
|
Nicolas Dwi Dharma |
License
Distributed under the MIT License. See LICENSE for more information.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Offline methodology engine for authorized penetration testing, CTF, and security research.
Enrich, search, assess, and manage threat intelligence through 80+ typed MCP tools.
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
Browser-local and CLI static evidence for deployed AI model artifacts.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceExposes read-only local analysis tools for source auditing, web traffic review, binary reverse engineering, exploit scaffolding, OSINT, and reporting via JSON-RPC over stdio, enabling LLMs to orchestrate evidence-based security workflows without executing targets or sending network requests.1MIT
- AlicenseAqualityCmaintenanceGives MCP clients such as Claude Code and OpenCode a static-analysis toolbox for binaries, executables, DLLs, shared objects, and web-app code, covering file identification and hashing, string extraction, PE/ELF/Mach-O/WASM parsing, disassembly, Ghidra decompilation, YARA scanning, and JavaScript deobfuscation. All inspection is read-only and never executes the target.16MIT

SpectraProbe MCP serverofficial
AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients and agents to drive SpectraProbe's static analysis engine over stdio, exposing twelve tools for probing targets, inspecting metadata, strings, dependencies, symbols, imports, resources and JavaScript, searching evidence, creating reports, listing providers and checking analysis status.2MIT- AlicenseNot gradedqualityBmaintenanceRead-only reverse-engineering toolkit exposed as 13 MCP tools for binary triage, strings, IOC extraction, disassembly, APK/firmware/PCAP analysis, and headless Ghidra decompilation. Missing backends are reported honestly as tool_missing rather than faked.2MIT
