sleuths-mcp
Related Servers
Alternatives to sleuths-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI assistants to analyze JVM thread dumps and GC logs, detecting deadlocks, lock contention, and GC pressure, without requiring a JVM runtime.740 npm2MIT
- AlicenseAqualityCmaintenanceEnables analysis of JVM thread dumps to detect deadlocks, CPU spikes, pool exhaustion, and virtual thread pinning, returning a health score and interactive report link.286 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets AI agents diagnose and debug live Java applications by auto-discovering JVMs and attaching Arthas to run diagnostic commands like thread, trace, watch, and ognl.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to review and compare Go goroutine dumps, surfacing goroutine leaks, lock pile-ups, exhausted database pools, and missing HTTP timeouts from dump text alone without connecting to the service.84 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to observe any running process — syscalls, CPU flamegraphs, thread stacks, sockets and file descriptors, packets, heap retainers, and container state — without breakpoints, restarts, or instrumentation. It turns output from local tools like strace, py-spy, perf, lsof, tcpdump, and gdb/lldb into structured findings that cite evidence, supporting guided triage of leaks, slowness, hangs, and crashes.106 npm14MIT
- AlicenseAqualityCmaintenanceLive .NET runtime diagnostics for AI assistants. Ask Claude to diagnose memory leaks, GC pressure, LOH fragmentation, and thread starvation in any running .NET process — no code changes required.72MIT
TDQS
Scored across 4 tools
Each tool targets a distinct JVM diagnostic artifact: thread dumps, exception logs, GC logs, and heap histograms. There is no meaningful overlap in purpose, so an agent can select the right tool from the input type alone.
All names follow a consistent snake_case verb_noun pattern. The verbs alternate between analyze and parse, but both are semantically appropriate and the structure remains highly predictable.
Four tools is well-scoped for a focused JVM diagnostics server. Each tool covers a distinct and commonly needed artifact, so none feels redundant or out of place.
The surface covers the core JVM troubleshooting artifacts: thread dumps, exception aggregation, GC logs, and heap histograms. Minor gaps exist around heap dump analysis and JFR-style profiling, but the main diagnostic workflows are supported.