Skip to main content
Glama
zlx-cyber

JADX-MCP-SERVER

by zlx-cyber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to JADX-MCP-SERVER

No user-submitted related servers found.

    Related Servers

    • AppUnpack MCP Server

      samalyxx
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to locally inspect Android APKs over MCP by decompiling Java, decoding resources, searching classes and methods, tracing references, and producing evidence reports with limitations.
      4
      MIT

    • dex-android-unpack

      TimeCyber
      A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to manage ADB devices and packages, detect packers, pull APKs, and unpack hardened Android apps via static extraction, BlackDex, or Frida, then convert DEX files to smali. Supports listing, reading, and regex-searching smali classes to locate APIs and other reverse-engineering targets.
      13
      381 npm
      1
      MIT

    • StaticApkAuditor MCP

      1111laaaddaaa
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -

    • jadx-rpc

      AsherDLL
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for analyzing Android APK, DEX, or JAR files via a headless jadx engine, enabling LLM agents to query decompiled code, symbols, call graphs, and more.
      2
      GPL 3.0

    • Android Source Explorer MCP

      kmikhailov90460
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI tools to retrieve and search actual AOSP and AndroidX source code on demand, including class lookup, method extraction, class members, hierarchy, source search, and optional cross-file navigation via LSP. It provides precise, offline-ready access to framework internals such as Activity lifecycle, ViewModel restoration, and Compose internals.
      -
    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

    B3.2/5.0

    Scored across 34 tools

    Disambiguation4/5

    Most tools map to clearly distinct JADX operations such as decompilation, search, rename, xrefs, comments, debug, and resources. There is some overlap: search_method_by_name overlaps search_classes_by_keyword when searching methods, and multiple class-source retrieval paths require reading scope carefully. Descriptions mostly resolve these, so misselection risk is moderate rather than high.

    Naming Consistency4/5

    Names are consistently snake_case and mostly follow a verb_noun pattern such as get_..., search_..., rename_..., add_..., list_..., and clear_.... Minor deviations exist: fetch_current_class uses fetch instead of get, and debug_* tools carry an extra group prefix, but the overall pattern remains predictable.

    Tool Count2/5

    34 tools is well above the typical tight MCP surface, and several groups such as search variants, main-application getters, and cache/debug helpers could be consolidated or made optional. The domain is broad, so not every tool is gratuitous, but the surface is heavy for an agent to navigate efficiently.

    Completeness5/5

    The tool set covers the reverse-engineering lifecycle: class/method/field/smali/source retrieval, package tree, keyword search, xrefs, renames, comments, manifest/resources, GUI selection, cache, and debug inspection. No obvious core operation is missing; remaining gaps are niche rather than workflow-blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources