MCP Server for Android APK Security Testing and Penetration Analysis
Server has 10 tools with complete schemas and descriptions, but quality is uneven. All tools follow verb_noun naming (analyze_, extract_, scan_, etc.) and have input schemas with type definitions. Descriptions are present (avg ~180 chars) and explain WHAT the tool does. However, critical gaps: (1) NO output schemas documented, LLMs cannot plan downstream calls or extract structured data; (2) parameters lack format/constraint details (e.g., 'apk_path' accepts any string, no validation guidance); (3) error handling is absent, no recovery guidance, no categorization of retryable vs fatal errors; (4) tool descriptions lack WHEN/WHY context and prerequisites (e.g., find_hardcoded_secrets requires jadx but doesn't state this clearly in description); (5) get_security_recommendations has NO required parameters, making it ambiguous when to call it. Baseline: avg tool description 194 chars (this server ~180), avg params 4 (this server 1-2), but 0% have documented return types vs 100% baseline for A+ tools.
Perform comprehensive security analysis on an Android APK file. This includes manifest analysis, permission scanning, component security assessment, hardcoded secret detection, certificate verification, and vulnerability detection. Returns detailed findings with severity ratings and remediation recommendations.
Analyze Android app components (Activities, Services, Receivers, Providers) for security issues. Checks for exported components, intent filters, and permission protections. Identifies potentially vulnerable component configurations.
Verify APK signature and extract certificate information. Validates the APK's digital signature and extracts certificate details including SHA-256 digest. Helps verify app authenticity and integrity.
Decompile APK to readable Java source code using jadx. Outputs decompiled source to a specified directory or temporary location. Useful for manual code review and deeper analysis.
Detect SSL/TLS configuration issues in the APK. Checks for cleartext traffic permissions, network security configuration, and potential SSL pinning bypass vulnerabilities.
No output schemas documented. LLMs cannot infer what fields each tool returns, blocking downstream tool chaining and structured data extraction. E.g., analyze_apk returns 'detailed findings' but structure is unknown.
Missing error handling and recovery guidance. No indication of which errors are retryable, what to do if APK is invalid, or how to handle missing jadx dependency. Agents cannot self-correct.
get_security_recommendations has no required parameters (vulnerability_type is optional). Ambiguous when to call it, should it return all recommendations, or require a specific vulnerability type? Description does not clarify.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | <=2025-11-25 | v2 |
Extract and parse the AndroidManifest.xml from an APK file. Returns package information, version details, SDK versions, and application configuration. Useful for quick inspection of app metadata without full analysis.
Search for hardcoded secrets in decompiled APK code. Detects API keys, passwords, tokens, AWS credentials, and other sensitive data. Uses pattern matching to identify common secret formats. Requires jadx to be installed for decompilation.
Generate a comprehensive security report for an APK. Combines all analysis results into a structured report with executive summary, detailed findings, vulnerability ratings, and remediation recommendations. Supports JSON output format.
Get security recommendations based on analysis findings. Provides actionable remediation steps for identified vulnerabilities aligned with OWASP MASVS and Mobile Security Testing Guide.
Analyze Android permissions requested by an APK. Categorizes permissions as dangerous, normal, or custom. Identifies potentially risky permissions that could compromise user privacy or device security.
Parameter descriptions lack format/constraint details. 'apk_path' accepts any string with no guidance on absolute vs relative paths, file existence validation, or error handling for missing files. Invites invalid input from LLMs.
Tool descriptions lack WHEN/WHY context and prerequisites. find_hardcoded_secrets mentions jadx requirement in description but does not state it as a prerequisite or error condition. Agents cannot plan ahead.