Skip to main content
Glama
Sign In
Reverence

Reverence

by 0x3k3h
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Reverence

No user-submitted related servers found.

    Related Servers

    • Nexus Unlock Everything

      OpsNexusDev
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to inspect and reverse-engineer native binaries, JavaScript/Electron apps, Go and Rust binaries, WASM, EVM bytecode, SQLite databases, and recorded crashes through a single MCP interface that bridges tools such as Ghidra, Frida, Hopper, binwalk, and jadx. Returns evidence-backed findings—pseudocode, symbols, strings, imports, routes, IPC boundaries—so agents can explain behavior and build similar features.
      MIT

    • Adversarial REA

      Cultistsid
      A
      license
      B
      quality
      B
      maintenance
      This MCP server lets an agent run local binary inspection on ELF, Mach-O, PE, APK, IPA, ASAR, WebAssembly, and firmware targets — pulling symbols, sections, classified strings, disassembly, and mitigation posture, and flagging dangerous imports and CWE patterns. It exposes eight stdio JSON-RPC tools (with no external API keys) that feed a multi-agent swarm for attack-surface mapping and exploit-chain synthesis.
      12
      MIT

    • binharness

      dougchansan
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to reverse-engineer binary files — hex viewing, disassembly, function/call-graph recovery, syscall and RTTI naming, string/xref search, and symbol export for Ghidra and IDA — across Switch NSO/NRO/NSP and many other formats. Tool output is persisted as annotations so analysis carries across sessions.
      MIT

    • Reverse Engineering MCP

      dockfixlabs
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes 18 typed tools that drive real static-analysis engines (Ghidra, apktool, WABT, TShark, evmole, Rizin) over a single MCP endpoint to decompile binaries, audit APKs, scan EVM contracts, inspect WebAssembly, firmware, SQLite, and pcap data. Every call returns signed, verifiable evidence with an evidence_id, provider identity, SHA-256 artifact digest, and explicit limitations for security research, malware analysis, forensics, and CTF work.
      MIT

    • rekit

      Amz34
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-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.
      2
      MIT

    • Jukeyman Unleashed

      jukeyman
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to take software apart over MCP — native binaries, Go/Rust/.NET assemblies, WASM and EVM bytecode, Android and Flutter apps, firmware, databases, crashes and network captures — returning findings backed by code, references and explicit unknowns. Drives deep-analysis engines such as Hopper, Ghidra, IDA, JADX and Frida entirely locally, letting agents explain behavior or rebuild a feature in your own project.
      496,689 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (pe_info vs elf_info vs macho_info, disassemble vs disassemble_entrypoint, radare2 vs ghidra_decompile). The one real overlap is `analyze`, which bundles identification, strings, and entry-point disassembly that identify_file, extract_strings, and disassemble_entrypoint also do alone, but the descriptions explicitly frame analyze as a triage entry point, which mitigates confusion.

    Naming Consistency4/5

    Nearly all tools use snake_case with a predictable verb_noun or noun_info shape (identify_file, extract_strings, pe_info, wasm_info, yara_scan). Minor deviations exist: `radare2` is a bare engine name, and `capabilities`/`analyze` are bare nouns/verbs rather than following the noun_info pattern, but the set remains readable and coherent.

    Tool Count4/5

    16 tools is reasonable for a multi-engine reverse-engineering toolkit covering several file formats and analysis techniques. Each tool maps to a distinct capability (per-format parsers, decompilers, scanners), though the count sits at the upper edge of the comfortable 3-15 range.

    Completeness4/5

    Strong lifecycle coverage for static binary analysis: identification, hashing/entropy, strings, hexdump, disassembly, per-format PE/ELF/Mach-O/WASM parsers, JS deobfuscation, YARA, radare2, and Ghidra decompilation. Minor gaps include no section/segment extraction or dumping and no WASM disassembly beyond metadata, but core read-only analysis workflows are well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources