jdwp-inspector

An MCP server that inspects Java programs using JDWP, Java's debugging protocol. It runs as a Java process and requires two timeout settings.

In plain words
What is it for?
Connecting an agent to the jdwp-inspector Java server with the required Java modules, log path, and timeout environment variables.
Why use it?
It provides an agent with a configured way to inspect a running Java debug session. The input does not specify which inspection operations are available.

MCP server for Claude CodeCodexCursorGemini CLIOpenCode

Part of the jdwp-debugging plugin — 2 skills, 1 hook, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add mcp/fgforrest/mcp-jdwp-java/jdwp-inspector
Clone the repo
git clone --depth 1 https://github.com/FgForrest/mcp-jdwp-java

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Or install jdwp-debugging, the plugin that ships this one along with the rest of its 2 skills, 1 hook, 1 MCP server.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade 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.

.mcp.json · 16 lines

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"
    }
  }
}
Changes

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.

  1. 3d ago First seen · 16 lines scan A 7f66effff5b5

Subscribe to this mod's changes

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.