mcp-jvm-diagnostics 0.1.7 → 0.1.8

package/build/index.js

@@ -13,7 +13,7 @@ import { parseJfrSummary } from "./parsers/jfr-summary.js";
 import { generateReportFromThreadDump, analyzeThreadDumpMarkdown, } from "./reporting.js";
 // Handle --help
 if (process.argv.includes("--help") || process.argv.includes("-h")) {
-    console.log(`mcp-jvm-diagnostics v0.1.7 — MCP server for JVM diagnostics
+    console.log(`mcp-jvm-diagnostics v0.1.8 — MCP server for JVM diagnostics
 
 Usage:
   mcp-jvm-diagnostics [options]
@@ -33,10 +33,10 @@ Tools provided:
 }
 const server = new McpServer({
     name: "mcp-jvm-diagnostics",
-    version: "0.1.7",
+    version: "0.1.8",
 });
 // --- Tool: analyze_thread_dump ---
-server.tool("analyze_thread_dump", "Parse a JVM thread dump (jstack output) and analyze thread states, detect deadlocks, identify lock contention hotspots, and find thread starvation patterns. Handles both platform threads and virtual threads (Java 21+).", {
+server.tool("analyze_thread_dump", "Parse a JVM thread dump (jstack output) and analyze thread states, detect deadlocks, identify lock contention hotspots, and find thread starvation patterns. Handles both platform threads and virtual threads (Java 21+). Note: deadlock detection covers synchronized monitor locks only — java.util.concurrent.locks.ReentrantLock and other j.u.c lock types do not expose their waiters in thread dump lock info and will not be detected.", {
     thread_dump: z
         .string()
         .describe("The full thread dump text (from jstack, kill -3, or VisualVM)"),
@@ -170,7 +170,7 @@ server.tool("analyze_gc_log", "Parse a JVM GC log and analyze garbage collection
 server.tool("analyze_heap_histo", "Parse jmap -histo output and detect memory leak candidates, object creation hotspots, classloader leaks, and heap composition issues.", {
     histo: z
         .string()
-        .describe("The jmap -histo output text (from jmap -histo <pid> or jmap -histo:live <pid>)"),
+        .describe("The jmap -histo output text. Use `jmap -histo:live <pid>` for leak detection — the :live flag forces a full GC first so only reachable objects appear, giving the clearest signal for leaks. Use `jmap -histo <pid>` (without :live) for a cheaper snapshot that includes unreachable objects not yet collected."),
 }, async ({ histo }) => {
     try {
         const report = parseHeapHisto(histo);

package/build/reporting.js

@@ -6,7 +6,7 @@ import { analyzeContention } from "./analyzers/contention.js";
 import { detectDeadlocks } from "./analyzers/deadlock.js";
 import { parseThreadDump } from "./parsers/thread-dump.js";
 const PRODUCT_NAME = "jvm-diagnostics";
-const TOOL_VERSION = "0.1.6";
+const TOOL_VERSION = "0.1.7";
 export const MISSING_LICENSE_INPUT_ERROR = "Missing required input: license_key";
 export const MISSING_THREAD_DUMP_ERROR = "Missing required input: thread_dump";
 export const MISSING_ENV_LICENSE_ERROR = "MCP_LICENSE_KEY environment variable is not set. generate_report requires a valid Pro license key. Free-tier analysis tools remain available without it.";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-jvm-diagnostics",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "MCP server for JVM diagnostics — analyze thread dumps, detect deadlocks, parse GC logs, and get JVM tuning recommendations",
   "mcpName": "io.github.dmitriusan/mcp-jvm-diagnostics",
   "author": "Dmytro Lisnichenko",
@@ -42,7 +42,7 @@
   ],
   "license": "MIT",
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=20.0.0"
   },
   "repository": {
     "type": "git",
@@ -55,11 +55,11 @@
   "dependencies": {
     "@mcp-java-suite/license": "npm:mcp-java-suite-license@^0.1.0",
     "@modelcontextprotocol/sdk": "^1.27.1",
-    "zod": "^3.24.2"
+    "zod": "^4.0.0"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
-    "typescript": "^5.8.2",
-    "vitest": "^4.0.18"
+    "typescript": "^6.0.0",
+    "vitest": "^4.1.0"
   }
 }