Skip to main content
Glama

Related Servers

Alternatives to mobile-re-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to analyze Android APK and iOS IPA files for security issues through natural language conversation, including permission auditing, secret detection, and SDK enumeration.
      12
      17 npm
      8
      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
    • 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.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      This is an MCP (Model Context Protocol) compatible tool that allows MobSF (Mobile Security Framework) to scan APK and IPA files directly via Claude, 5ire, or any MCP-capable client.
      24
      MIT
    • 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

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    Android and iOS tools are cleanly separated by platform prefix, and each tool targets a distinct artifact (manifest, permissions, entitlements, secrets, google-services, frameworks, native libs). Minor overlap exists between the secrets scanners and the google-services tools, both of which perform pattern scanning over plists/resources, but the descriptions delineate them adequately.

    Naming Consistency4/5

    Names are consistently snake_case with a platform prefix (android_, apk_, ios_) followed by the target artifact, which is readable and predictable. The mix of apk_ and android_ prefixes for what is essentially the same platform is a small deviation from a single uniform convention.

    Tool Count5/5

    14 tools is squarely within a well-scoped range and each tool corresponds to a distinct static-analysis step on APK or IPA files. No tool feels redundant or padding.

    Completeness4/5

    The surface covers the core mobile RE workflow: manifest/plist parsing, permissions, entitlements, secrets, embedded SDKs, native libraries, endpoint extraction, and APK diffing. Gaps remain—no certificate/signing verification, no iOS binary diff counterpart to apk_diff, and no network security config parsing—but these are workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues