Skip to main content
Glama

Related Servers

Alternatives to Fris Reverse MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      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.
      4
      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
      B
      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.
      18
      19
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to analyze Android APK and iOS IPA files for security issues through natural language, including permission auditing, API endpoint extraction, hardcoded secret detection, Firebase inspection, and third-party SDK enumeration.
      12
      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/5.0

    Scored across 12 tools

    Disambiguation4/5

    Tools target distinct phases (inventory, analysis, artifact reading, manifest review, header inspection), and descriptions carefully scope boundaries. However, inspect_apk vs analyze_apk vs inspect_headers vs review_manifest could still be confused by an agent at first glance, since they all operate on APK contents with subtle differences.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (inspect_apk, analyze_apk, list_artifacts, read_artifact, review_manifest, compare_apks, search_artifacts, summarize_job, install_tools). Two outliers—capabilities and doctor—deviate from the pattern but are readable and contextually sensible.

    Tool Count5/5

    Twelve tools map well to a coherent APK static-analysis workflow: setup (doctor, install_tools, capabilities), analysis (inspect_apk, analyze_apk, inspect_headers, compare_apks, review_manifest), and evidence handling (list_artifacts, read_artifact, search_artifacts, summarize_job). Each tool appears to earn its place.

    Completeness4/5

    The surface covers the core lifecycle: environment checks, engine installation, inspection, analysis job creation, artifact inventory/read/search, comparison, manifest review, and summary. Minor gaps exist—no explicit job cleanup/deletion or artifact export tool—but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues