# JProfiler (npm · @ej-technologies/jprofiler-mcp)

Java profiling with AI agent integration. Profile CPU, memory, JDBC, HTTP and more.

- Trust score: 67/100 (medium)
- Change this week: +42
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-06

## Components

- npm · `@ej-technologies/jprofiler-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/ej-technologies-jprofiler-mcp/ej-technologies-jprofiler-mcp.md), [page](https://verifymcp.io/servers/ej-technologies-jprofiler-mcp/ej-technologies-jprofiler-mcp)

## Channel facts

- Registry: `npm`
- Package: `@ej-technologies/jprofiler-mcp`
- Version: `16.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-06.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 94 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN https://www.ej-technologies.com/jprofiler/license) isn't a recognized OSI-approved license.
  - Actively maintained (last published 20 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1339 tokens (~148/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add ej-technologies-jprofiler-mcp -- npx -y @ej-technologies/jprofiler-mcp
```

### Codex

```bash
codex mcp add ej-technologies-jprofiler-mcp -- npx -y @ej-technologies/jprofiler-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ej-technologies-jprofiler-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ej-technologies/jprofiler-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ej-technologies-jprofiler-mcp --command npx --arg -y --arg @ej-technologies/jprofiler-mcp
```

### Hermes

```yaml
mcp_servers:
  ej-technologies-jprofiler-mcp:
    command: "npx"
    args: ["-y", "@ej-technologies/jprofiler-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "ej-technologies-jprofiler-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ej-technologies/jprofiler-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-06 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security fell 1.

### 2026-08-04 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Supply Chain Security rose 1.

### 2026-08-02 (score 65, +46)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] License: unverified → fail
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: SEE LICENSE IN https://www.ej-technologies.com/jprofiler/license

### 2026-08-01 (score 19, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 26, +1)

- [security regression] Malware scan: pass → unverified
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Dependency health: partial → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-29 (score 25, −19)

- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Dependency health: unverified → partial

### 2026-07-28 (score 44, +20)

- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: unverified
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fail

### 2026-07-27 (score 24)

First indexed and scored.

## MCP tools (9)

### `prepare_profiling` (~203 tokens)

Prepare a profiling session by retrieving a JVM parameter to be added to a Java process call to record performance data with stack traces for the following subsystems: cpu, jdbc, jpa, http_server, http_client, mongo_db. The result is a JSON object containing a 'jvmParameter' to be added (quoted) to the Java process at startup. Add it verbatim and do not create or modify any files; the configuration is already set up for you. Run the Java process; the recording is saved automatically when the JVM terminates (or after the optional maximum duration). Then call check_status to access the data - do not load the saved snapshot file yourself.

Input parameters:

- `delay` (integer): An optional recording delay in seconds measured from the jvm start.
- `maximumDuration` (integer): An optional maximum recording duration in seconds. If not specified, data will be saved at JVM termination or when check_status is called with 'stopRecording: true'.

### `load_snapshot` (~127 tokens)

Load an existing .jps, .hprof, or .jfr file for analysis. You must call check_status to check the loading progress and - after this returns 'data_ready' - retrieve data with the get_* tools. To compare two performance snapshots, load both in a single call: set filePath to the run to analyze and baselineFilePath to the baseline; The get_performance_hotspots tool then report the differences.

Input parameters:

- `baselineFilePath` (string): An optional baseline snapshot for performance comparisons
- `filePath` (string, required): The absolute path to the snapshot file

### `attach` (~152 tokens)

Attach to a running JVM by PID or to a JVM inside a Docker container. Records performance data for the following subsystems: cpu, jdbc, jpa, http_server, http_client, mongo_db until check_status is called with 'stopRecording: true'. You can use list_jvms to discover JVMs.

Input parameters:

- `containerNameOrId` (string): The name or ID of a Docker container. When specified, profiling attaches to a JVM inside this container.
- `pid` (integer): The PID of a local JVM process, or the container PID (NSpid) of a JVM inside the specified container. If a container is specified and this is omitted, the topmost JVM in the container is used.

### `check_status` (~70 tokens)

Check the status of a profiling session and discover which subsystems were recorded. Can be used to stop recording. When the data is ready provides information about the recorded subsystems (e.g. cpu, jdbc, http_client).

Input parameters:

- `stopRecording` (boolean): Optionally request the recording to be stopped now.

### `get_performance_hotspots` (~177 tokens)

Retrieve a sorted list of top performance hotspots. Returns a JSON object containing an array of hotspots with timing data and expansion ids. Use expand_performance_hotspot to drill down.

Input parameters:

- `packageFilter` (string): Optional comma-separated package filter to focus on classes of interest.
- `subsystem` (string, required): The subsystem (as provided by check_status, for example cpu or jdbc) to analyze.
- `view` (string): The view type: either 'hotspots' (the default) to focus on the methods/statements that most time is spent in or 'call_tree' to get a structural view of the time spent.
- `wallTime` (boolean): Optional, used for the cpu subsystem only: If true, time spent in all thread states will be used, otherwise only the runnable state is used. Defaults to false.

### `expand_performance_hotspot` (~63 tokens)

Expand a performance hotspot or call tree. Returns a JSON object containing the back trace of a hot spot or the children of the call tree node with the provided id.

Input parameters:

- `id` (integer, required): The id of the hotspot or call tree node to be expanded

### `create_heap_dump` (~157 tokens)

Dump the heap of a locally running JVM or of a JVM inside a Docker container to an HPROF file and load it for analysis. You must call check_status to check the loading progress and - after this returns 'data_ready' - retrieve data with get_heap_data. You can use list_jvms to discover JVMs.

Input parameters:

- `containerNameOrId` (string): The name or ID of a Docker container. When specified, profiling attaches to a JVM inside this container.
- `pid` (integer): The PID of a local JVM process, or the container PID (NSpid) of a JVM inside the specified container. If a container is specified and this is omitted, the topmost JVM in the container is used.

### `get_heap_data` (~127 tokens)

Retrieve aggregated data of a heap dump. Can show biggest objects, retained class lists, and class histograms.

Input parameters:

- `biggestObjectId` (integer): If view is retained_classes, supply the ID of the biggest object from the biggest_objects view.
- `packageFilter` (string): Optional comma-separated package filter to focus on classes of interest.
- `view` (string): The view type: either biggest_objects (the default) to get a list of biggest objects, retained_classes to show a retained class list for a single biggest object, or classes for a class histogram for…

### `list_jvms` (~62 tokens)

List locally running JVMs or JVMs running in a Docker container with their command line and PID. Use the information to call attach or create_heap_dump.

Input parameters:

- `containerNameOrId` (string): Optionally specify the name or ID of a Docker container.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ej-technologies-jprofiler-mcp/ej-technologies-jprofiler-mcp#diagnostics

## Score history

- 2026-08-06: 67
- 2026-08-05: 66
- 2026-08-04: 66
- 2026-08-03: 65
- 2026-08-02: 65
- 2026-08-01: 19
- 2026-07-31: 26
- 2026-07-29: 25
- 2026-07-28: 44
- 2026-07-27: 24

## Links

- npm package: https://www.npmjs.com/package/@ej-technologies/jprofiler-mcp
- Socket report: https://socket.dev/npm/package/@ej-technologies/jprofiler-mcp
- Repository: https://github.com/ej-technologies/jprofiler-mcp
- Changelog RSS feed: https://verifymcp.io/servers/ej-technologies-jprofiler-mcp/ej-technologies-jprofiler-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ej-technologies-jprofiler-mcp/ej-technologies-jprofiler-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ej-technologies-jprofiler-mcp/ej-technologies-jprofiler-mcp