Java JAR Decompiler & Reverse Engineering MCP Server
Related Servers
Alternatives to Java JAR Decompiler & Reverse Engineering MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceDecompiles Java .class files, packages, and JARs into readable source code, enabling AI assistants to inspect Java bytecode.327 npm20ISC
- AlicenseBqualityCmaintenanceEnables AI tools to analyze Java dependencies by scanning Maven projects, decompiling JAR files, and extracting detailed class information including methods, fields, and inheritance relationships. Solves the problem of AI hallucinations when generating code that calls external dependencies by providing accurate class structures through decompilation.316 npm41Apache 2.0
- AlicenseAqualityBmaintenanceDecompiles Maven dependencies into readable Java source directly inside your AI agent.1027 npm1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to reverse-engineer software across native binaries, managed code, Electron apps, websites, and live runtime behavior, returning findings linked to the evidence and limitations behind each conclusion. It also maintains a durable workspace where those behaviors can be inspected, questioned, compared against real execution, and exported as runnable handoffs.538,483 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables offline Android package analysis by loading APK, DEX, JAR, class, and XAPK files to inspect app metadata, manifests, classes, methods, resources, strings, and cross-references, and to export decompiled Java sources through CRUDE MCP-AQL tools.AGPL 3.0
- AlicenseNot gradedqualityNot gradedmaintenanceEnables agents to inspect native binaries, JavaScript/Electron apps, .NET assemblies, and websites without source code, trace runtime behavior, and return evidence-backed findings for explaining features or building similar implementations.538,483 npmMIT
TDQS
Scored across 9 tools
Each tool targets a distinct stage of the decompilation workflow (decompile, list, analyze, AST, mavenize, compile, compare, rename, pipeline). Despite some conceptual overlap between standalone tools and the pipeline, the descriptions clearly differentiate their scope and usage.
All tool names follow a consistent snake_case verb_noun pattern (e.g., decompile_jar, list_decompilers, compile_maven_project). The naming style is uniform and predictable across the entire set.
9 tools is well-scoped for a decompilation and reverse engineering server, covering each necessary step without being excessive. The count falls comfortably within the ideal 3-15 range.
The tool surface covers the full reverse engineering lifecycle: decompile, analyze, generate AST, mavenize, compile, compare, and rename. No obvious gaps hinder the core workflow, and the pipeline tool provides an end-to-end path.