MCP server for static security analysis of Android source code
MCP server for static security analysis of Android application source code. Runs on Cloudflare Workers as a remote MCP server over Streamable HTTP. Analyzes Android project source files — without building the project — and returns a structured security report. The analysis covers: Manifest analysis — exported components, dangerous permissions, cleartext traffic, debug flags, backup settings, SDK…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
analyze_android_projectNo description publishedThis tool published no description. Forge does not invent one.
explain_findingNo description publishedThis tool published no description. Forge does not invent one.
healthNo description publishedThis tool published no description. Forge does not invent one.
list_android_security_checksNo description publishedThis tool published no description. Forge does not invent one.
0 of 4 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for static security analysis of Android application source code. Runs on Cloudflare Workers as a remote MCP server over Streamable HTTP. Analyzes Android project source files — without building the project — and returns a structured security report. The analysis covers: Manifest analysis — exported components, dangerous permissions, cleartext traffic, debug flags, backup settings, SDK versions Gradle/build config — release build misconfigurations, outdated SDKs, suspicious…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.