jar-tools-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_jar_securityA | Run jar.tools' static security scan on a local .jar/.zip or .class file. Returns structured findings — suspicious-class counts by category (network activity, file access, process execution, hard-to-review/obfuscated code) plus decompiler-anomaly signals. Useful for auditing a dependency before adding it to a build, or investigating a suspicious plugin/mod. Static analysis only — the file is never executed. Free for .jar/.zip up to 64MB and .class up to 5MB; pass a Pro license_key to raise the JAR size cap to 256MB. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
The single tool name 'scan_jar_security' follows a clear verb_noun pattern, consistent with good naming conventions.
With only one tool, the server is minimal. While it may suffice for a focused use case, the count is at the low end of reasonable scope.
The single tool covers the core functionality of static security scanning, returning structured findings. Minor gaps like retrieving past scan results or managing licenses are not addressed, but it handles the primary action well.