Skip to main content
Glama
droidasc-mcp

droidasc-mcp

by cnlnn

Related Servers

Alternatives to droidasc-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      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.
      5
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables an AI runtime to perform authorized static analysis of Android APKs over local MCP stdio, inspecting inventories, DEX/ELF headers and manifest details while decompiling with verified, checksum-pinned JADX and Apktool engines it can bootstrap itself. Reports results as evidence-backed observations, with literal text search, two-APK comparison and Markdown summaries, without ever executing the target APK.
      12
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes the ASC APK-as-database analysis engine as MCP tools, enabling AI clients to run fast cross-reference searches, string/secret recon, class and member inspection, manifest and component extraction, and parallel batch queries across many APKs without full decompilation. All tools are stateless and process-isolated, so multiple clients can query single or multiple APK analysis sessions concurrently.
      MIT
    • 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
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI agents with a unified MCP interface for Android APK reverse engineering, metadata analysis, Smali/resource editing, rebuilding, signing, verification, and ADB device testing.
      MIT

    TDQS

    B3.4/5.0

    Scored across 18 tools

    Disambiguation3/5

    The set has notable overlap: asc_analyze_dex and asc_query_dex_session expose many of the same reference/member/string query capabilities, and the simple asc_list_classes/asc_get_class_source/asc_find_refs tools partially duplicate session-query behavior. Descriptions clarify session vs one-shot and artifact vs DEX contexts, but an agent can still hesitate between several tools.

    Naming Consistency4/5

    Names consistently use the asc_ prefix and snake_case, with mostly predictable verb_noun patterns such as asc_list_classes, asc_get_class_source, and asc_open_dex_session. A few are noun phrases or state/report style (asc_apk_info, asc_manifest_summary, asc_secret_candidates), which is a minor deviation.

    Tool Count3/5

    Eighteen tools is on the heavy side for a single MCP server, and the overlap between one-shot DEX analysis, session queries, and artifact inspection suggests some could be consolidated. The Android/DEX analysis domain is complex enough to justify many capabilities, but the surface feels borderline bloated rather than tightly scoped.

    Completeness4/5

    The surface covers a broad static-analysis lifecycle: class/source discovery, references, sessions, manifests, signing inventory, APK entries, artifact inspection, DEX diffing, and secret candidates. Missing native/ELF analysis, resource resolution, and dynamic/runtime verification are acknowledged scope limits rather than silent gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data