Skip to content

Android Security Analyzer MCP server

io.github.ako2345/android-security-analyzerako2345streamable-httpv1.0.0Scanned

MCP server for static security analysis of Android source code

4 tools: 4 only read.

Tools: 0 delete, 0 irreversible, 0 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Android Security Analyzer MCP server can do

The Android Security Analyzer MCP server is published by the GitHub account ako2345. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

1 tool reads private data (analyze_android_project).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Only reads 4Show 4 read-only tools
  • analyze_android_projectAnalyzes an Android project's source code for security vulnerabilities.Reads private data1 finding

    Why it is in this group

    • The name "analyze_android_project" says "analyze": a word for reading.

    What it can reach

    • private-dataThe input names a file (input.files), and the tool reads: it reads files.

    Findings

    • Info

      The input schema at properties.options.properties.enableSecretScan.description mentions "credential".

      Matched text

      inputSchema.properties.options.properties.enableSecretScan.description: "Enable secret/credential scanning (default: true)"

      What this check looks for
    Description, as the server wrote 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.
  • explain_findingExplains a specific security finding by its rule ID.No findings

    Why it is in this group

    • The name "explain_finding" says "explain": a word for reading.
    Description, as the server wrote it
    Explains a specific security finding by its rule ID. Returns why it is a risk, how to fix it, and false positive considerations.
  • healthReturns the server health status, version, and rule engine statistics.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns the server health status, version, and rule engine statistics.
  • list_android_security_checksReturns the list of all implemented security checks/rules with their IDs, categories, severity levels, and descriptions.No findings

    Why it is in this group

    • The name "list_android_security_checks" says "list": a word for reading.
    Description, as the server wrote it
    Returns the list of all implemented security checks/rules with their IDs, categories, severity levels, and descriptions.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:01 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The input schema at properties.options.properties.enableSecretScan.description mentions "credential".

    Matched text

    inputSchema.properties.options.properties.enableSecretScan.description: "Enable secret/credential scanning (default: true)"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__android-security-analyzer__analyze_android_project",
      "mcp__android-security-analyzer__list_android_security_checks",
      "mcp__android-security-analyzer__explain_finding",
      "mcp__android-security-analyzer__health"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as android-security-analyzer. Review it before you use it.

Capability tags behind 1 rule
  • mcp__android-security-analyzer__analyze_android_project private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ako2345/android-security-analyzer/verify?hash=77cc4a5a2d8a42ce6bcd17b8087a6243f30cec0e299d9fdb47d58532d1aa1e36" | jq -e '.changed == false'

Pinned hash 77cc4a5a2d8a, from Nov 16, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ako2345/android-security-analyzer/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ako2345/android-security-analyzer
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ako2345/android-security-analyzer.svg)](https://radar.anlyon.com/servers/io.github.ako2345/android-security-analyzer)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:22 UTC.

Android Security Analyzer MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Android Security Analyzer MCP server safe?

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 1 finding from fixed checks. Read-only tools can still pass private data to a model.

Can the Android Security Analyzer MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Android Security Analyzer MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Android Security Analyzer MCP server have?

4 tools: 4 read. analyze_android_project, list_android_security_checks, explain_finding and health.

Does the Android Security Analyzer MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Android Security Analyzer MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Android Security Analyzer MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.