# unerr (npm · @unerr-ai/unerr)

Operational memory for AI agents: code graph, session memory & guardrails. No context rot.

- Trust score: 12/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-10

> **Malware flagged**: A supply-chain scanner flagged a high-severity malware risk in this package. Treat it as unsafe to install until the finding is cleared.

## Components

- npm · `@unerr-ai/unerr`: 12/100 (this document), [markdown](https://verifymcp.io/servers/unerr-ai-unerr/unerr-ai-unerr.md), [page](https://verifymcp.io/servers/unerr-ai-unerr/unerr-ai-unerr)

## Channel facts

- Registry: `npm`
- Package: `@unerr-ai/unerr`
- Version: `0.2.1`
- 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-10.

- **Supply Chain Security**: 37/100
  - Malware check failed: a supply-chain vendor flagged a high-severity malware risk.
  - CVE check failed: a known medium-severity CVE affects @anthropic-ai/sdk 0.82.0, a direct dependency. A fixed version is available.
  - Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does.
  - Dependency health was assessed across the 400 of 455 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 6/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license.
  - Actively maintained (last published 18 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

**Unverified: 4 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### Claude

```bash
claude mcp add unerr-ai-unerr -- npx -y @unerr-ai/unerr
```

### Codex

```bash
codex mcp add unerr-ai-unerr -- npx -y @unerr-ai/unerr
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add unerr-ai-unerr --command npx --arg -y --arg @unerr-ai/unerr
```

### Hermes

```yaml
mcp_servers:
  unerr-ai-unerr:
    command: "npx"
    args: ["-y", "@unerr-ai/unerr"]
```

### Other

```json
{
  "mcpServers": {
    "unerr-ai-unerr": {
      "command": "npx",
      "args": [
        "-y",
        "@unerr-ai/unerr"
      ]
    }
  }
}
```

## 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-07 (score 12, +2)

- [security regression] CVE-2026-59871 affects this package: medium
- [security regression] CVE-2026-23950 affects this package: medium
- [security regression] CVE-2026-59874 affects this package: medium
- [security regression] CVE-2026-59875 affects this package: medium
- [security regression] GHSA-r292-9mhp-454m affects this package: medium
- [security regression] CVE-2026-29786 affects this package: medium
- [security regression] CVE-2026-23745 affects this package: medium
- [security regression] CVE-2026-24842 affects this package: medium
- [security regression] CVE-2026-31802 affects this package: medium
- [security regression] CVE-2026-59873 affects this package: medium
- [security regression] CVE-2026-53655 affects this package: medium
- [security regression] CVE-2026-26960 affects this package: medium

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

- [security regression] CVE-2026-16729 affects this package: medium
- [security regression] CVE-2026-16728 affects this package: medium
- [security regression] CVE-2026-15157 affects this package: medium

### 2026-08-03 (score 11, +2)

No change was recorded against any check on this day. Supply Chain Security went from 27 to 32.

### 2026-08-02 (score 9, +9)

- [security regression] CVE-2026-12151 affects this package: medium
- [security regression] CVE-2026-9679 affects this package: medium
- [security regression] CVE-2026-1526 affects this package: medium
- [security regression] CVE-2026-1525 affects this package: medium
- [security regression] CVE-2026-6733 affects this package: medium
- [security regression] CVE-2026-11525 affects this package: medium
- [security regression] CVE-2026-22036 affects this package: medium
- [security regression] CVE-2026-1527 affects this package: medium
- [security regression] CVE-2026-2229 affects this package: medium
- [security regression] CVE-2026-41686 affects this package: medium
- [security regression] Provenance: unverified → fail
- [security regression] Known CVEs: unverified → fail
- [security regression] Malware scan: unverified → fail
- [security improvement] Install scripts: unverified → partial
- [security] Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.
- [security] The scripts that run when this package is installed changed: postinstall
- [functional regression] License: unverified → fail
- [functional regression] Dependency health: partial → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional] Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.
- [functional] Licence: Elastic-2.0

### 2026-08-01 (score 0, 0)

- [functional improvement] Dependency health: unverified → partial

### 2026-07-31 (score 0, 0)

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

### 2026-07-30 (score 0, −5)

- [security regression] Malware scan: fail → unverified
- [security improvement] Malware indicator (automated code analysis) cleared
- [functional regression] Dependency health: partial → unverified
- [functional] Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.
- [functional] Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.

### 2026-07-28 (score 5, +1)

No change was recorded against any check on this day. Supply Chain Security went from 12 to 13.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/unerr-ai-unerr/unerr-ai-unerr#diagnostics

## Score history

- 2026-08-10: 12
- 2026-08-09: 12
- 2026-08-08: 12
- 2026-08-07: 12
- 2026-08-06: 10
- 2026-08-05: 10
- 2026-08-04: 10
- 2026-08-03: 11
- 2026-08-02: 9
- 2026-08-01: 0
- 2026-07-31: 0
- 2026-07-30: 0
- 2026-07-28: 5
- 2026-07-27: 4
- 2026-07-26: 2

## Links

- npm package: https://www.npmjs.com/package/@unerr-ai/unerr
- Socket report: https://socket.dev/npm/package/@unerr-ai/unerr
- Changelog RSS feed: https://verifymcp.io/servers/unerr-ai-unerr/unerr-ai-unerr.xml
- Changelog JSON feed: https://verifymcp.io/servers/unerr-ai-unerr/unerr-ai-unerr.json
- HTML version of this page: https://verifymcp.io/servers/unerr-ai-unerr/unerr-ai-unerr