Skip to main content
Glama
sapyyy

Java JAR Decompiler & Reverse Engineering MCP Server

by sapyyy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Java JAR Decompiler & Reverse Engineering MCP Server

No user-submitted related servers found.

    Related Servers

    • Java Class Analyzer MCP Server

      handsomestWei
      A
      license
      B
      quality
      C
      maintenance
      Enables 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.
      3
      12 npm
      43
      Apache 2.0

    • java-class-analyzer-mcp

      Aorls
      A
      license
      A
      quality
      D
      maintenance
      Enables AI to analyze Java classes from Maven project dependencies, with support for decompilation strategies and configurable groupId mappings.
      3
      5 npm
      5
      MIT

    • jadx-rpc

      AsherDLL
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for analyzing Android APK, DEX, or JAR files via a headless jadx engine, enabling LLM agents to query decompiled code, symbols, call graphs, and more.
      2
      GPL 3.0

    • Java JAR MCP Server

      biggerball
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to look up Java class definitions and list dependencies from Maven projects by analyzing local JAR files via the Model Context Protocol.
      4 npm
      4
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources