# APSA mobile app security audit

> APSA mobile app security audit is an open-source MCP server for security. Local, evidence-graded security audits of Android and iOS source, APK, AAB and IPA files. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, macOS, Linux, self-hosted
- **Repository:** https://github.com/ictechgy/apsa
- **MCP Registry name:** io.github.ictechgy/apsa
- **Categories:** [security](https://ai-powered.com/categories/security), [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

APSA audits your own mobile apps by inspecting source code and built packages (APK, AAB, IPA), correlating public vulnerability information, and keeping evidence, coverage and report history together. Its name joins app and audit, and it merges the earlier Quaygate lint engine and Mobile Audit workflows. Use it from the CLI, from a terminal UI (`apsa tui`), or through MCP and reusable skills.

The README is candid about limits. Coverage separates execution gaps (`partial`, exit 3) from precision limits of the bounded static model (`limited`), and a threshold failure (exit 4) takes precedence over an incomplete audit. Every AAB audit stays partial, embedded IPA metadata does not authenticate signatures, and declared Gradle versions remain candidates until resolved-build evidence is supplied.

The parser runs under macOS Seatbelt or Linux bubblewrap when available, and records when isolation is unavailable. Model-facing report pages are bounded and carry guidance to treat app evidence as untrusted. Waivers, approved baselines and policy decisions support team and CI use, and 1.7.0 changes CI exit semantics, so review the upgrade notes before reusing older baselines.

## Features

- **Source and package audits:** Inspects Android and iOS source plus APK, AAB and IPA builds.
- **Evidence and coverage tracking:** Reports record what was and was not analysed, with partial and limited states.
- **Dependency advisories:** Correlates public vulnerability data, including OSV, with app dependencies.
- **Sandboxed parsing:** Parser isolation via Seatbelt or bubblewrap, recorded in the report.
- **Baselines and waivers:** Approved baselines and waivers with recorded severity for CI.
- **Multiple interfaces:** CLI, terminal UI, MCP server and reusable skills share one engine.

## Good for

- Audit your own Android or iOS app build before release
- Let a coding agent run a security review and read bounded report pages
- Gate CI on severity thresholds and compare against a baseline
- Check packaged apps for plaintext credentials and weak crypto patterns

## Install

### Claude Code (Terminal)

```sh
claude mcp add apsa -- uvx apsa
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "apsa": {
      "command": "uvx",
      "args": [
        "apsa"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "apsa": {
      "command": "uvx",
      "args": [
        "apsa"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "apsa": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "apsa"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "apsa": {
      "command": "uvx",
      "args": [
        "apsa"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "apsa": {
      "command": "uvx",
      "args": [
        "apsa"
      ]
    }
  }
}
```

## FAQ

### Does it run locally?

Yes. The registry description calls the audits local and the server runs over stdio.

### What file types does it analyse?

Source code and APK, AAB and IPA builds.

### How are CI failures reported?

In 1.7.0, execution gaps give exit 3, a threshold failure exits 4 and takes precedence, and limited coverage exits 0 unless strict coverage is set.

### Is there a desktop app?

Not yet. The README describes a desktop roadmap and points to the terminal UI for now.

### Is APSA mobile app security audit free?

Yes. APSA mobile app security audit is open source, so you can use and self-host it for free.

### How do I add APSA mobile app security audit to Claude Code?

Run this command in your terminal: claude mcp add apsa -- uvx apsa

### What are the best alternatives to APSA mobile app security audit?

The closest alternatives to APSA mobile app security audit are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.

## Where this comes from

- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [REA](https://ai-powered.com/mcp/rea): REA is an open-source MCP server for developer tools.
- [Context7](https://ai-powered.com/mcp/context7): Context7 is a freemium MCP server for developer tools.
- [Chrome DevTools MCP](https://ai-powered.com/mcp/chrome-devtools-mcp-2): Chrome DevTools MCP is an open-source MCP server for browser automation.
- [Codebase Memory](https://ai-powered.com/mcp/codebase-memory): Codebase Memory is an open-source MCP server for knowledge and memory.
- [GitHub](https://ai-powered.com/mcp/github-2): GitHub is an open-source MCP server for developer tools.
- [Serena MCP: the IDE for your agent](https://ai-powered.com/mcp/serena-mcp-the-ide-for-your-agent): Serena MCP: the IDE for your agent is an open-source MCP server for developer tools.
- [awesome-mcp-servers](https://ai-powered.com/mcp/awesome-mcp-servers-2): awesome-mcp-servers is an open-source MCP server for developer tools.
- [XERJ](https://ai-powered.com/mcp/xerj): XERJ is an open-source MCP server for knowledge and memory.

---
Source: https://ai-powered.com/mcp/apsa-mobile-app-security-audit
