# io.github.yamaru-eu/hardware-probe (npm · @yamaru-eu/hardware-probe)

Hardware probe for performance diagnostics, thermal monitoring, and LLM optimization.

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

## Components

- npm · `@yamaru-eu/hardware-probe`: 67/100 (this document), [markdown](https://verifymcp.io/servers/yamaru-eu-hardware-probe/yamaru-eu-hardware-probe.md), [page](https://verifymcp.io/servers/yamaru-eu-hardware-probe/yamaru-eu-hardware-probe)

## Channel facts

- Registry: `npm`
- Package: `@yamaru-eu/hardware-probe`
- Version: `1.1.2`
- 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**: 87/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 95 of 99 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 95 of 99 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: no license is declared.
  - Actively maintained (last published 86 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 459 tokens (~41/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 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 yamaru-eu-hardware-probe -- npx -y @yamaru-eu/hardware-probe
```

### Codex

```bash
codex mcp add yamaru-eu-hardware-probe -- npx -y @yamaru-eu/hardware-probe
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yamaru-eu-hardware-probe": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@yamaru-eu/hardware-probe"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add yamaru-eu-hardware-probe --command npx --arg -y --arg @yamaru-eu/hardware-probe
```

### Hermes

```yaml
mcp_servers:
  yamaru-eu-hardware-probe:
    command: "npx"
    args: ["-y", "@yamaru-eu/hardware-probe"]
```

### Other

```json
{
  "mcpServers": {
    "yamaru-eu-hardware-probe": {
      "command": "npx",
      "args": [
        "-y",
        "@yamaru-eu/hardware-probe"
      ]
    }
  }
}
```

## 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-05 (score 67, +2)

- [security improvement] CVE-2026-69207 no longer affects this package
- [security improvement] Known CVEs: fail → partial

### 2026-08-04 (score 65, −1)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-03 (score 66, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 63, +58)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [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] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100

### 2026-08-01 (score 5, −2)

- [functional regression] Dependency health: partial → unverified

### 2026-07-31 (score 7, −33)

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

### 2026-07-30 (score 40, −36)

- [security regression] Install scripts: pass → unverified
- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: partial → unverified
- [security regression] Provenance: fail → unverified
- [functional regression] Dependency health: partial → unverified
- [functional regression] License: fail → unverified
- [functional regression] Maintenance: pass → unverified

### 2026-07-27 (score 76, +51)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional regression] Security disclosure: unverified → fail
- [functional regression] License: unverified → fail
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 100
- [functional] First check of Schema quality: good
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: fail

## MCP tools (11)

### `analyze_local_system` (~32 tokens)

Reads the hardware specifications of the local machine: CPU, RAM, motherboard and OS. Returns a structured JSON object.

### `analyze_performance` (~25 tokens)

Provides real-time system performance: CPU load, memory usage, and top processes.

### `analyze_inference_config` (~45 tokens)

Performs a deep scan for LLM inference optimization: GPU details, real memory bandwidth benchmark, ML runtimes (Ollama, Docker, WSL), and environment variables.

### `get_inference_expert_knowledge` (~42 tokens)

Returns the expert instructions and rules for optimizing LLM inference on this specific hardware. Call this to learn HOW to interpret analyze_inference_config results.

### `check_llm_compatibility` (~70 tokens)

(BETA) Checks if a specific LLM model can run on this machine. Returns optimal quantization and estimated tokens per second. Requires remote API connection.

Input parameters:

- `model_name` (string, required): LLM model name (e.g., 'Llama 3.1 70B')

### `get_llm_recommendations` (~56 tokens)

(BETA) Recommends the best LLM models that can run locally on this machine. Requires remote API connection.

Input parameters:

- `limit` (number): Max recommendations
- `use_case` (string): Use case

### `analyze_ram_pressure` (~31 tokens)

Reports current memory pressure: total/used/free/available memory, swap usage, and top processes by RSS.

### `check_storage_health` (~34 tokens)

Reports per-disk health: type (NVMe/SSD/HDD), vendor, temperature, SMART status, and firmware.

### `thermal_profile` (~26 tokens)

Reports current CPU and GPU thermal and frequency state: temperature, utilization, and fan speed.

### `diagnose_antivirus_impact` (~31 tokens)

Detects running antivirus/EDR products and reads their exclusion rules. Checks dev hot paths coverage.

### `monitor_system_health` (~67 tokens)

Monitors system metrics (CPU, RAM, Thermal) over a specified duration and returns statistical summary. Useful for diagnosing transient issues during high-load tasks.

Input parameters:

- `duration_seconds` (number): Monitoring duration in seconds (max 60)
- `interval_seconds` (number): Sampling interval in seconds

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/yamaru-eu-hardware-probe/yamaru-eu-hardware-probe#diagnostics

## Score history

- 2026-08-06: 67
- 2026-08-05: 67
- 2026-08-04: 65
- 2026-08-03: 66
- 2026-08-02: 63
- 2026-08-01: 5
- 2026-07-31: 7
- 2026-07-30: 40
- 2026-07-28: 76
- 2026-07-27: 76
- 2026-07-26: 25

## Links

- npm package: https://www.npmjs.com/package/@yamaru-eu/hardware-probe
- Socket report: https://socket.dev/npm/package/@yamaru-eu/hardware-probe
- Repository: https://github.com/yamaru-eu/hardware-probe
- Changelog RSS feed: https://verifymcp.io/servers/yamaru-eu-hardware-probe/yamaru-eu-hardware-probe.xml
- Changelog JSON feed: https://verifymcp.io/servers/yamaru-eu-hardware-probe/yamaru-eu-hardware-probe.json
- HTML version of this page: https://verifymcp.io/servers/yamaru-eu-hardware-probe/yamaru-eu-hardware-probe