APSA mobile app security audit vs Solana Security Standard
A side-by-side look at the APSA mobile app security audit and Solana Security Standard MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
APSA mobile app security auditSecurityLocal, evidence-graded Android/iOS security audits of source, APK, AAB and IPA for AI agents.36FairAuth: no auth requiredVerdict: choose APSA mobile app security audit for security work; choose Solana Security Standard for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose APSA mobile app security audit when
- You need dedicated capabilities in the Security domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
APSA_PARSER_SANDBOX.
Choose Solana Security Standard when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A APSA mobile app security audit | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 36/100 · Fair | 44/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | APSA_PARSER_SANDBOX | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 38 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View APSA mobile app security audit | View Solana Security Standard |
Tools & capabilities
APSA mobile app security audit tools
No tool names declared yet. Check the project README from the listing page.
Solana Security Standard tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
APSA mobile app security audit
No confirmed install command for APSA mobile app security audit yet — follow the setup steps linked from its listing page rather than a guessed package name.
Solana Security Standard
{
"mcpServers": {
"solana-security-standard": {
"command": "npx",
"args": [
"-y",
"@jelleo/solana-security-standard"
]
}
}
}
Frequently asked questions
APSA mobile app security audit is categorized under Security and uses an install path we have not confirmed yet. Solana Security Standard belongs to Security and uses a local stdio subprocess. Pick APSA mobile app security audit for security work and Solana Security Standard for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. APSA mobile app security audit has no confirmed install command yet — follow its own setup instructions.
APSA mobile app security audit is listed as free. Auth: no auth required. Solana Security Standard has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add apsa-mobile-app-security-audit and solana-security-standard as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, APSA mobile app security audit has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Solana Security Standard has 44/100 (Fair) with 1 views, 0 installs and 38 GitHub stars.