1. Conduid
  2. Security
  3. Jvm Incident Agent
MCP server · Security

Jvm Incident Agent

by · github.com/JingYu-create520/jvm-incident-agent

JVM incident analysis from thread dumps, GC logs and heap histograms - deterministic rules, evidence chain on every finding, runs offline.

Unclaimed ai-agentscli-tooldeadlockdevopsgcheap-dumpjavajvmmcpmodel-context-protocolobservabilityperformance-analysisspring-bootthread-dump
InstallView source
34Low

Scored 21 days ago · breakdown

About Jvm Incident Agent

Jvm Incident Agent is an MCP server published by JingYu-create520 in the Security category: jVM incident analysis from thread dumps, GC logs and heap histograms - deterministic rules, evidence chain on every finding, runs offline.

The repository has 1 stars and 0 forks, with the last commit 25 days ago. Recent commit activity is the strongest signal that reported issues will get attention.

Install

From source
git clone https://github.com/JingYu-create520/jvm-incident-agent

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Jvm Incident Agent

Powered by Claude · Grounded in docs

I know everything about Jvm Incident Agent. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Releases

v0.4.0jvm-incident-agent 0.4.0 — a rule that could not measure now says so · 22 Sep 2026"Every rule ran clean against this snapshot." That sentence was printed whenever the findings table came out empty — including when six rules had returned nothing because the input was too thin to measure anything at all. A truncated GC…
v0.3.4jvm-incident-agent 0.3.4 — a log with no clock can no longer read as an all-clear · 22 Sep 2026`EXC003 — Exception burst` has always documented its limit: it needs ten parseable timestamps and returns nothing without them. True, and useless at 4 a.m. — the report is what gets read, and in it *"no exception burst"* arrived in…
v0.3.3jvm-incident-agent 0.3.3 — a JDK 7 CMS log, and three numbers that were counted for the wrong thing · 22 Sep 2026A JDK 7 CMS log — the shape still running under a lot of legacy services — produced this: CRITICAL GCA003 "Across 5 major collections the heap low-water mark is 21M, sits at 5 of 5 collections with 100% of the heap still live after a…
v0.3.2jvm-incident-agent 0.3.2 — a coloured log and a half-read window now tell you so · 22 Sep 2026Two inputs that produced a *missing* finding instead of a wrong one — which is the harder kind to notice, because the report looks finished. A log a terminal coloured is still a log Redirecting a Spring Boot process into a file — `nohup`,…
v0.3.1jvm-incident-agent 0.3.1 — a healthy Spring Boot startup is not a Full GC storm · 22 Sep 2026The README has promised since 0.1.0 that a startup `Metadata GC Threshold` Full GC is not an incident. Only one rule knew. Slice the first 9.7 seconds off a healthy Parallel GC service — 78 real lines, two Full GCs at uptime 1.0 s and 2.1…
Questions

About Jvm Incident Agent

How do I install Jvm Incident Agent?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Jvm Incident Agent safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Jvm Incident Agent still maintained?

Yes — the latest release is v0.4.0 (22 Sep 2026), and the last commit was 25 days ago. The repository has 1 stars.