No user-submitted related servers found.
Scored across 17 tools
Several tools overlap heavily around the core reverse-engineering workflow: omni_triage_target, omni_auto_orchestrate, omni_deep_reverse, and omni_inspect_symbol all perform detection, disassembly, decompilation, or unpacking to varying degrees. omni_inspect_symbol is an especially broad catch-all that duplicates capabilities also exposed by omni_dynamic_probe, omni_symbolic_protocol, omni_advanced_native, and omni_patch_cfg_memory, making tool selection ambiguous for an agent.
All tool names use the same omni_ prefix and snake_case convention, giving the set a predictable visual pattern. The suffixes mix verb_noun and descriptive noun phrases rather than following a strict verb_noun scheme, but the naming remains readable and mostly consistent.
Seventeen tools is slightly heavy for a typical MCP surface, though the broad reverse-engineering domain can justify a larger set. The bigger issue is granularity: many entries are mega-tools bundling multiple unrelated capabilities, so the count feels less intentionally scoped than it could be.
The surface covers a wide reverse-engineering lifecycle: triage, static and dynamic analysis, mobile and native targets, unpacking, symbolic solving, patching, memory scanning, session management, and annotation export. Minor gaps exist around explicit reporting or guided format discovery, but the core domain is well covered.