Skip to main content
Glama
boy-offi9-inc

HexForge Gateway

by boy-offi9-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to HexForge Gateway

No user-submitted related servers found.

    Related Servers

    • jadx-rpc

      AsherDLL
      A
      license
      Not graded
      quality
      B
      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

    • JADX-MCP-SERVER

      bartest5
      A
      license
      Not graded
      quality
      C
      maintenance
      Fully automated MCP server built to communicate with JADX-AI-MCP Plugin to analyze Android APKs using LLMs like Claude — uncover vulnerabilities, parse manifests, and reverse engineer effortlessly.
      1
      Apache 2.0

    • APK-MCP

      tkb-bit
      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
    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

    A3.9/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool targets a distinct action and resource: decode vs decompile are clearly differentiated by rebuildability, adb_* tools each handle a specific adb operation, and frida_trace vs frida_list_processes cover different dynamic analysis aspects. No two tools appear to do the same thing.

    Naming Consistency4/5

    The majority of tools follow a verb_noun snake_case pattern (decode_apk, build_apk, scan_secrets). Minor deviations like 'adb_devices' and 'chat_with_workspace' break the pure verb_noun pattern but are still understandable and predictable given the tool's domain.

    Tool Count4/5

    With 19 tools, this is slightly on the high side of the ideal range, but each tool serves a distinct purpose in the APK analysis and dynamic instrumentation workflow. The count is justified by the breadth of static analysis, file management, ADB, and Frida capabilities, and none feel redundant.

    Completeness4/5

    The tool surface covers the full lifecycle of APK analysis: static decoding/decompiling, rebuilding, packer identification, secret scanning, code search, dynamic analysis via ADB and Frida, plus workspace and knowledge management. Minor gaps like a signing tool (explicitly noted as external) and perhaps a network capture tool prevent a perfect score, but the core workflows are well supported.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources