# Android Security Analyzer (remote · android-security-analyzer.ako-labs.workers.dev)

MCP server for static security analysis of Android source code

- Trust score: 60/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `android-security-analyzer.ako-labs.workers.dev`: 60/100 (this document), [markdown](https://verifymcp.io/servers/ako2345-android-security-analyzer/android-security-analyzer.md), [page](https://verifymcp.io/servers/ako2345-android-security-analyzer/android-security-analyzer)

## Channel facts

- Endpoint: `https://android-security-analyzer.ako-labs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 239 tokens (~59/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ako2345-android-security-analyzer https://android-security-analyzer.ako-labs.workers.dev/mcp
```

### Codex

```toml
[mcp_servers.ako2345-android-security-analyzer]
url = "https://android-security-analyzer.ako-labs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ako2345-android-security-analyzer": {
      "type": "remote",
      "url": "https://android-security-analyzer.ako-labs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ako2345-android-security-analyzer --url https://android-security-analyzer.ako-labs.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ako2345-android-security-analyzer:
    url: "https://android-security-analyzer.ako-labs.workers.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ako2345-android-security-analyzer": {
      "type": "http",
      "url": "https://android-security-analyzer.ako-labs.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 58, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 59, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 58)

First indexed and scored.

## MCP tools (4)

### `analyze_android_project` (~93 tokens)

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.

Input parameters:

- `files` (array, required): Array of project files to analyze
- `options` (object): Analysis options
- `projectName` (string, required): Name of the Android project being analyzed

### `list_android_security_checks` (~61 tokens)

Returns the list of all implemented security checks/rules with their IDs, categories, severity levels, and descriptions.

Input parameters:

- `category` (string): Filter rules by category (manifest, gradle, source, xml-config, secret). Leave empty for all rules.

### `explain_finding` (~65 tokens)

Explains a specific security finding by its rule ID. Returns why it is a risk, how to fix it, and false positive considerations.

Input parameters:

- `findingId` (string, required): The rule/finding ID (e.g., MAN-001, SRC-003, SEC-002)

### `health` (~20 tokens)

Returns the server health status, version, and rule engine statistics.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ako2345-android-security-analyzer/android-security-analyzer#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 58
- 2026-07-30: 60
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 58

## Links

- Remote endpoint: https://android-security-analyzer.ako-labs.workers.dev/mcp
- Repository: https://github.com/ako2345/android-security-analyzer
- Changelog RSS feed: https://verifymcp.io/servers/ako2345-android-security-analyzer/android-security-analyzer/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ako2345-android-security-analyzer/android-security-analyzer/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ako2345-android-security-analyzer/android-security-analyzer