Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/idachev/mcp-javadcWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/idachev/mcp-javadc/javadc)<a href="https://agentmods.dev/mcp/idachev/mcp-javadc/javadc"><img src="https://agentmods.dev/badge/mcp/idachev/mcp-javadc/javadc.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
javadc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"javadc": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@idachev/mcp-javadc"
],
"env": {}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 11 lines scan A a04b192dae48
javadc is an MCP server published in the GitHub repository idachev/mcp-javadc (20 stars, last pushed 1y ago), licensed ISC. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
dejared
Java decompiler MCP server for AI coding agents. Explore, search, and decompile JAR, WAR, EAR, and AAR bytecode with CFR, Vineflower, or Procyon. Runs locally from the dejared-mcp npm package.
mcp-jvm-diagnostics
MCP server for JVM diagnostics — analyze thread dumps, detect deadlocks, parse GC logs, and get JVM tuning recommendations. Runs locally from the mcp-jvm-diagnostics npm package.
java-decompile-mcp
MCP server for Java class and jar file decompilation using CFR. Runs locally from the java-decompile-mcp Python package.
mcp-java-dev-tools
MCP server "mcp-java-dev-tools" as configured in nimbly-dev/mcp-java-dev-tools. Runs locally from the mcp-java-dev-tools npm package.
java-class-analyzer-mcp-server
MCP server "java-class-analyzer-mcp-server" as configured in ETHAN0430/java-class-analyzer-mcp. Runs locally from the @yifei/java-class-analyzer-mcp-server npm package.
jdwp-mcp
Debug live JVMs through JDWP — from any MCP-compatible agent. Runs locally from the jdwp-mcp Python package.