Skip to main content
Glama

Related Servers

Alternatives to apsa

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to drive the complete mobile security toolkit—static/dynamic analysis, Frida hooks, runtime exploration, traffic interception, network setup, and IoT scans—through engine-exposed tools.
      3
      GPL 3.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to run security-focused operations such as network scanning, binary and symbol analysis, string extraction, live/pcap traffic inspection, and sandboxed command execution through an MCP client.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to run and track scans, inspect quota usage, redeem existing studio report rights, and list or download generated reports through the associated REST API. It operates locally over stdio with API-key authentication and bounded retry/polling behavior.
      24 npm
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, especially across audit, intelligence, runtime, jobs, and policy domains. The main ambiguity is within the reports_* cluster and between audit_scan and audit_start, where descriptions are needed to avoid misselection.

    Naming Consistency4/5

    Names are consistently snake_case and grouped by domain prefixes such as reports_, audit_, runtime_, intelligence_, and jobs_. Minor inconsistency appears in action ordering, e.g. reports_compare versus verify_finding, and a few tools such as capabilities lack a domain prefix.

    Tool Count3/5

    24 tools is heavy and lands in the borderline 16-25 range. The complex mobile-audit domain justifies many of them, but several report and job helpers make the surface feel somewhat sprawling.

    Completeness4/5

    The tool set covers the core audit lifecycle: scanning, persistent audits, reassessment, dependency checks, finding verification, reporting, history, policy evaluation, and job control. Minor gaps remain around creating waivers/checklists and actually executing runtime test scenarios, but agents can largely work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues