Skip to main content
Glama
alejandrojlamas

apk-docforge

by alejandrojlamas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to apk-docforge

No user-submitted related servers found.

    Related Servers

    • APK Security Guard MCP Suite

      il-il1
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides a one-stop automated solution for Android APK security analysis by integrating tools like JEB, JADX, APKTOOL, FlowDroid, and MobSF into unified MCP standard API interfaces.
      11
      -

    • 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.
      -

    • MalDroid

      yayaya142
      A
      license
      Not graded
      quality
      B
      maintenance
      Local static-analysis assistant for Android malware research that manages investigation cases, exposes MCP tools via a local server, and persists evidence-backed findings without cloud dependency.
      MIT

    • droidasc-mcp

      cnlnn
      A
      license
      A
      quality
      A
      maintenance
      Enables safe, read-only analysis of Android APKs through six typed MCP tools, including manifest decoding, class listing, source decompilation, and reference searching, with paginated structured output and strict path/timeout limits.
      6
      1
      Apache 2.0
    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.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct stage or artifact: search/download handle acquisition, analyze_artifact creates the analysis, and the get/list tools expose distinct outputs such as findings, features, screens, reports, or prompts. There are no overlapping tool purposes that would confuse an agent.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_*, download_*, analyze_*, get_*, and list_*. The get_ vs list_ split is also consistent: get_ returns a single item or document, while list_ returns a collection.

    Tool Count5/5

    Nine tools is an appropriate size for an APK analysis pipeline. Every tool maps to a distinct workflow step or output artifact, and none feel redundant or extraneous.

    Completeness4/5

    The pipeline covers the full lifecycle needed for APK docforge work: search, download, analysis, report generation, prompt generation, and detailed findings/feature/screen listings. The only minor gap is the absence of a general list_analyses or candidate-management tool, which could limit discoverability but does not break the core workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources