Android Security Analyzer is an MCP server published by io.github.ako2345, hosted at android-security-analyzer.ako-labs.workers.dev. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 4 tools, including analyze_android_project, list_android_security_checks, explain_finding, health.
MCP server for static security analysis of Android source code
Nothing else in the archive shares these values.
Inferred from the host name and headers: what a server runs on, not who runs it.
Analyzes an Android project's source code for security vulnerabilities. Accepts project files (AndroidManifest.xml, build.gradle, Java/Kotlin sources, XML configs) and returns a structured security report with findings, severity scores, and recommendations.
| Parameter | Type | Description |
|---|---|---|
| files * | array | Array of project files to analyze |
| options | object | Analysis options |
| projectName * | string | Name of the Android project being analyzed |
{
"name": "analyze_android_project",
"description": "Analyzes an Android project's source code for security vulnerabilities. Accepts project files (AndroidManifest.xml, build.gradle, Java/Kotlin sources, XML configs) and returns a structured security report with findings, severity scores, and recommendations.",
"inputSchema": {
"type": "object",
"required": [
"projectName",
"files"
],
"properties": {
"files": {
"type": "array",
"items": {
"type": "object",
"required": [
"path",
"content"
],
"properties": {
"path": {
"type": "string",
"description": "Relative file path within the project (e.g., app/src/main/AndroidManifest.xml)"
},
"content": {
"type": "string",
"description": "File content as text"
}
}
},
"description": "Array of project files to analyze"
},
"options": {
"type": "object",
"properties": {
"maxFileSizeKb": {
"type": "number",
"description": "Maximum file size in KB to process (default: 512)"
},
"enableSecretScan": {
"type": "boolean",
"description": "Enable secret/credential scanning (default: true)"
},
"includeInfoLevel": {
"type": "boolean",
"description": "Include informational findings (default: true)"
}
},
"description": "Analysis options"
},
"projectName": {
"type": "string",
"description": "Name of the Android project being analyzed"
}
}
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Returns the list of all implemented security checks/rules with their IDs, categories, severity levels, and descriptions.
| Parameter | Type | Description |
|---|---|---|
| category | string | Filter rules by category (manifest, gradle, source, xml-config, secret). Leave empty for all rules. |
{
"name": "list_android_security_checks",
"description": "Returns the list of all implemented security checks/rules with their IDs, categories, severity levels, and descriptions.",
"inputSchema": {
"type": "object",
"properties": {
"category": {
"enum": [
"manifest",
"gradle",
"source",
"xml-config",
"secret"
],
"type": "string",
"description": "Filter rules by category (manifest, gradle, source, xml-config, secret). Leave empty for all rules."
}
}
}
}Explains a specific security finding by its rule ID. Returns why it is a risk, how to fix it, and false positive considerations.
| Parameter | Type | Description |
|---|---|---|
| findingId * | string | The rule/finding ID (e.g., MAN-001, SRC-003, SEC-002) |
{
"name": "explain_finding",
"description": "Explains a specific security finding by its rule ID. Returns why it is a risk, how to fix it, and false positive considerations.",
"inputSchema": {
"type": "object",
"required": [
"findingId"
],
"properties": {
"findingId": {
"type": "string",
"description": "The rule/finding ID (e.g., MAN-001, SRC-003, SEC-002)"
}
}
}
}Returns the server health status, version, and rule engine statistics.
No parameters.
{
"name": "health",
"description": "Returns the server health status, version, and rule engine statistics.",
"inputSchema": {
"type": "object",
"properties": {}
}
}Names, descriptions and schemas were written by the server and are shown as data.