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

    • JADX-MCP-SERVER

      bartest5
      A
      license
      B
      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.
      32
      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
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.9/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools target distinct resource+action pairs and the descriptions explicitly cross-reference each other (decompile_apk vs decode_apk, scan_secrets vs search_code, chat_with_workspace vs summarize_text). The only mild overlaps are in the reading surface: list_knowledge (which includes reports), get_report and list_findings all expose findings-like content, and get_graph_entity vs list_graph_entities require reading the descriptions to pick correctly.

    Naming Consistency4/5

    Almost everything follows a verb_noun pattern (list_findings, create_finding, verify_finding, read_file, search_code) or a domain-prefixed variant (adb_*, frida_*) that stays readable. Minor deviations like adb_devices (noun-only, unlike list_workspaces) and frida_list_processes (prefix before verb) break the pattern slightly but never cause confusion.

    Tool Count3/5

    29 tools is heavy, though the server genuinely spans several sub-domains: workspaces, findings, knowledge graph, file ops, apktool, adb, Frida and AI helpers. Each tool is individually justified, but the surface is at the upper bound of what an agent can hold in context comfortably.

    Completeness3/5

    Coverage is broad (workspace lifecycle, findings create/update/verify/report, decompile/decode/build, device and Frida operations), but there are real dead ends: build_apk produces an unsigned APK and adb_install rejects unsigned APKs, yet no sign_apk tool exists, so the edit-rebuild-install loop can't be closed. There are also no delete operations for findings, artifacts or workspaces.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources