re-audit-mcp
Related Servers
Alternatives to re-audit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables an AI runtime to perform authorized static analysis of Android APKs over local MCP stdio, inspecting inventories, DEX/ELF headers and manifest details while decompiling with verified, checksum-pinned JADX and Apktool engines it can bootstrap itself. Reports results as evidence-backed observations, with literal text search, two-APK comparison and Markdown summaries, without ever executing the target APK.12MIT
- AlicenseBqualityCmaintenanceEnables local, evidence-first triage of native binaries by extracting bounded symbols, strings, sections, call sites, gadget candidates, and mitigation signals as MCP tools for agent-guided manual review. It also provides metadata-only inspection for carriers such as archives, WebAssembly, firmware, and scripts without claiming verified vulnerabilities.125MIT
- 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.-
- AlicenseAqualityAmaintenanceEnables 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.121,327 npm1MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to perform autonomous Android security analysis, including static analysis, dynamic analysis, and Frida instrumentation, powered by MobSF.4MIT
- AlicenseCqualityAmaintenanceEnables AI agents to inspect APKs and resources, analyze native libraries, trace runtime behavior with Frida, and connect app screen actions to code through ADB.89MIT
TDQS
Scored across 6 tools
Each scan_* tool targets a distinct analysis dimension (strings, secrets, mitigations, APK manifest), so boundaries are mostly clear. The only overlap is intentional: full_audit orchestrates the same checks, and an agent could be unsure whether to call it or the granular tools for a single check.
Names are snake_case with predictable verb_noun structure (detect_file_type, scan_strings, scan_secrets, scan_binary_mitigations, scan_apk). full_audit is the one deviation, lacking a verb prefix, but it stays within the same convention and remains readable.
Six tools is well-scoped for a static binary/APK audit server: one aggregator plus five focused analyzers. No tool feels redundant or missing at this granularity.
The surface covers file typing, strings, secrets, native mitigations, and APK manifest issues for ELF/PE/Mach-O/APK. Minor gaps: detect_file_type recognizes JAR but no JAR-specific scan exists, and APK signing/certificate verification is absent, though agents can work around these.