apsa
Related Servers
Alternatives to apsa
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables security scanning of source code and Apple configuration files, providing evidence-based findings, explanations, remediation plans, threat modeling, and knowledge base access through MCP tools.MIT
- FlicenseBqualityCmaintenanceEnables local-first static and optional controlled dynamic analysis of Android APK artifacts, with provenance-aware downloads, Markdown reports, and structured security findings via MCP stdio tools.9-
- AlicenseNot gradedqualityAmaintenanceEnables 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.1GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables 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.MIT
- AlicenseAqualityAmaintenanceEnables MCP clients to run deterministic AST safety audits, secret scanning, and sandboxed test execution on codebases, with human approval required before any remediation action.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables authorized Android security testing with static and dynamic analysis, Frida instrumentation, storage inspection, and traffic interception via MCP tools.1MIT
TDQS
Scored across 17 tools
Most tools target clearly distinct resources and actions, and descriptions clarify boundaries well. The main risk is mild overlap among audit_scan, audit_start, and audit_reassess, plus reports_get/list/compare, but each has a defined role.
Tool names consistently use snake_case and domain prefixes such as reports_, jobs_, intelligence_, and audit_. A few names are noun-oriented rather than verb_noun, but the overall convention is predictable.
At 17 tools the server is slightly above the ideal 3-15 range, but the surface covers several legitimate areas: auditing, intelligence, jobs, reports, runtime, and policy. Each tool appears to earn its place without obvious redundancy.
The set covers core audit lifecycle operations, cached intelligence access, report reading/comparison, background job control, dependency checks, and runtime planning. Minor gaps remain, such as policy CRUD or report deletion/export, but these are not fatal for the apparent domain.