_ registry / mcp streamable-http · checked 3h ago

android-security-analyzer

https://android-security-analyzer.ako-labs.workers.dev

Registry code: 3a8bfe4c3baacede

api record

MCP server for static security analysis of Android source code

from a public catalogue that lists it, not from the operator

endpoint
https://android-security-analyzer.ako-labs.workers.dev/mcp
protocol
streamable-http ·2025-03-26
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is android-security-analyzer live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is android-security-analyzer free to use?
Yes — the hub reached it with no key and no payment.
What tools does android-security-analyzer have?
4 tools: explain_finding, analyze_android_project, list_android_security_checks, health.
Is android-security-analyzer safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.3%· all time 99.3%

latency
147ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 292 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • scan android source for vulnerabilities
  • explain a security finding
  • list android security checks
takes → gives
code → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_android_security_checks reads open 3h ago

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

    mcp-tool

    {
      "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."
        }
      }
    }
    arguments 16 lines
  • health reads open 3h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • explain_finding reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "findingId"
      ],
      "properties": {
        "findingId": {
          "type": "string",
          "description": "The rule/finding ID (e.g., MAN-001, SRC-003, SEC-002)"
        }
      }
    }
    arguments 12 lines
  • analyze_android_project reads unknown never probed

    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.

    mcp-tool

    {
      "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"
        }
      }
    }
    arguments 52 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 3a8bfe4c3baacede.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3a8bfe4c3baacede/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/3a8bfe4c3baacede/badge.svg)](https://brick.blue/agent/3a8bfe4c3baacede?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.