Fris Reverse MCP
Related Servers
Alternatives to Fris Reverse MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to locally inspect Android APKs over MCP by decompiling Java, decoding resources, searching classes and methods, tracing references, and producing evidence reports with limitations.4MIT
- FlicenseBqualityCmaintenanceEnables local-first static and optional controlled dynamic analysis of Android APK artifacts, with provenance-aware downloads, Markdown reports, and structured security findings via MCP stdio tools.9-
- FlicenseNot gradedqualityBmaintenanceEnables Android APK security auditing through natural language by decompiling APKs with Apktool and running static analysis heuristics for attack surface, permissions, secrets, crypto, native libraries, and more, with every analysis logged to disk as markdown reports.-
- AlicenseBqualityAmaintenanceEnables safe, read-only analysis of Android APKs through six typed MCP tools, including manifest decoding, class listing, source decompilation, and reference searching, with paginated structured output and strict path/timeout limits.1819Apache 2.0
- AlicenseAqualityBmaintenanceEnables MCP-compatible AI clients to analyze Android APK and iOS IPA files for security issues through natural language, including permission auditing, API endpoint extraction, hardcoded secret detection, Firebase inspection, and third-party SDK enumeration.12MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with a unified MCP interface for Android APK reverse engineering, metadata analysis, Smali/resource editing, rebuilding, signing, verification, and ADB device testing.MIT
TDQS
Scored across 12 tools
Tools target distinct phases (inventory, analysis, artifact reading, manifest review, header inspection), and descriptions carefully scope boundaries. However, inspect_apk vs analyze_apk vs inspect_headers vs review_manifest could still be confused by an agent at first glance, since they all operate on APK contents with subtle differences.
Most tools follow a clear verb_noun pattern (inspect_apk, analyze_apk, list_artifacts, read_artifact, review_manifest, compare_apks, search_artifacts, summarize_job, install_tools). Two outliers—capabilities and doctor—deviate from the pattern but are readable and contextually sensible.
Twelve tools map well to a coherent APK static-analysis workflow: setup (doctor, install_tools, capabilities), analysis (inspect_apk, analyze_apk, inspect_headers, compare_apks, review_manifest), and evidence handling (list_artifacts, read_artifact, search_artifacts, summarize_job). Each tool appears to earn its place.
The surface covers the core lifecycle: environment checks, engine installation, inspection, analysis job creation, artifact inventory/read/search, comparison, manifest review, and summary. Minor gaps exist—no explicit job cleanup/deletion or artifact export tool—but core workflows are covered.