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.
npx agentmods add mcp/fgforrest/mcp-jdwp-java/jdwp-inspectorgit clone --depth 1 https://github.com/FgForrest/mcp-jdwp-javaGrade A, and why
jdwp-inspector 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 3d 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
{
"jdwp-inspector": {
"command": "java",
"args": [
"--add-modules",
"jdk.jdi,jdk.attach",
"-DLOG_PATH=${CLAUDE_PLUGIN_ROOT}/logs/mcp-jdwp-inspector.log",
"-jar",
"${CLAUDE_PLUGIN_ROOT}/jdwp-mcp-server/target/mcp-jdwp-java.jar"
],
"env": {
"MCP_TIMEOUT": "30000",
"MCP_TOOL_TIMEOUT": "120000"
}
}
}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.
- 3d ago First seen · 16 lines scan A 7f66effff5b5
jdwp-inspector is an MCP server published in the GitHub repository FgForrest/mcp-jdwp-java (24 stars, last pushed 1mo ago), licensed MIT. 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
jdbg
MCP server "jdbg" as configured in PieceOfFall/jdbg. Launched with jdbg __mcp.
jdwp-mcp
Debug live JVMs through JDWP — from any MCP-compatible agent. Runs locally from the jdwp-mcp Python package.
jlink-mcp
Debug embedded firmware on real hardware: J-Link probes, Cortex-M faults, RTT logs, GDB. Runs locally from the jlink-mcp npm package. Needs 4 environment variables to run.
jlink
MCP server "jlink" as configured in Klievan/jlink-mcp. Runs out/mcp/standalone.js with node.
x64dbg
MCP server for x64dbg debugger - 23 mega-tools for AI-powered reverse engineering and debugging. Runs locally from the x64dbg-mcp-server npm package. Needs 2 environment variables to run.
qwen-dap-mcp
Native runtime and crash-dump debugging through a local DAP-to-MCP bridge for coding agents. Runs locally from the @slp-dev1/qwen-dap-mcp npm package.