Skip to main content
Glama
ictechgy

apsa

by ictechgy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to apsa

No user-submitted related servers found.

    Related Servers

    • msrf

      keyuraghao
      A
      license
      Not graded
      quality
      A
      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.
      2
      GPL 3.0

    • kali-mcps

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

    • @wolf-agents/mcp

      wolf-agents
      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.
      38 npm
      Apache 2.0

    • SentinelMCP

      Terrytd0
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to scan codebases, persist and prioritize security findings against SLAs, retrieve CVE details, propose fixes, and create tickets through its tools. It also supports agent-assisted remediation drafting while enforcing human approval and preventing auto-merge.
      1
      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

    B3.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools target clearly distinct resources and actions, and the descriptions clarify boundaries well. However, audit_scan/audit_start/audit_reassess and reports_get/reports_followup/reports_history/reports_compare overlap enough that an agent may hesitate without reading the full descriptions.

    Naming Consistency4/5

    The set predominantly follows a snake_case category_action convention (jobs_*, reports_*, audit_*, intelligence_*), making tool families predictable. Minor deviations are the bare capabilities tool and the verb-first verify_finding.

    Tool Count3/5

    24 tools is heavy for a single MCP server, sitting in the borderline 16-25 range. The mobile security audit domain is broad, but some report and job tools could plausibly be consolidated.

    Completeness4/5

    The surface covers scanning, persistent jobs, report retrieval/follow-up/compare/history/checklist/SARIF ingest/baseline export, intelligence, dependency checks, spec validation, finding verification, runtime planning/devices, and policy evaluation. Minor gaps such as report deletion or cleanup and explicit approval workflow details are workaroundable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources