Java Inspector
Related Servers
Alternatives to Java Inspector
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI to analyze Java classes from Maven project dependencies, with support for decompilation strategies and configurable groupId mappings.12 npm5MIT
- AlicenseBqualityBmaintenanceEnables 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 npm42Apache 2.0
- AlicenseAqualityFmaintenanceDecompiles Java .class files, packages, and JARs into readable source code, enabling AI assistants to inspect Java bytecode.334 npm20ISC
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to look up Java class definitions and list dependencies from Maven projects by analyzing local JAR files via the Model Context Protocol.10 npm4MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that scans Maven project dependencies, decompiles Java class files, and provides class structure analysis to LLMs for accurate code generation.6Apache 2.0
- FlicenseAqualityAmaintenanceEnables decompilation and reverse engineering of Java JAR files through multi-engine decompilation, candidate evaluation, Maven project structuring, AST-based deobfuscation, and bytecode comparison.491-
TDQS
Scored across 10 tools
Each tool targets a distinct resource and action: project scanning, JAR discovery, JAR inspection, class search, code search, implementation lookup, class inspection, dependency explanation, resource search, and resource reading. No two tools have overlapping purposes; even search_class and search_code differ clearly by scope (indexed classes vs. code constructs).
All tool names follow a consistent verb_noun pattern with descriptive verbs (scan, find, inspect, search, explain, read). The pattern is uniform across the set, making it easy to predict tool behavior from the name alone.
The 10 tools are well-scoped for a Java inspector/analyzer server, covering project-level scanning, artifact lookup, detailed inspection, and search operations. Each tool serves a distinct purpose without redundancy, and the count is ideal for the domain.
The tool surface covers the full read/analyze lifecycle: scan, find, inspect, search, explain, and read. Minor gaps exist such as no explicit 'list_jar_contents' top-level tool or dependency listing shortcut, but these are accessible via inspect_jar and explain_dependency, so agents can work around them.