# Yaver (npm · yaver-cli)

Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.

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

## Components

- npm · `yaver-cli`: 26/100 (this document), [markdown](https://verifymcp.io/servers/yaver-io-yaver/yaver-cli.md), [page](https://verifymcp.io/servers/yaver-io-yaver/yaver-cli)

## Channel facts

- Registry: `npm`
- Package: `yaver-cli`
- Version: `1.99.398`
- 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-03.

- **Supply Chain Security**: 73/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 0.6.1, reached via yaver-mobile-headless > @modelcontextprotocol/sdk. 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.
  - Only part of the dependency tree could be resolved (16 of 17), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- **Capabilities**: 0/100
  - Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.

**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 yaver-io-yaver -- npx -y yaver-cli
```

### Codex

```bash
codex mcp add yaver-io-yaver -- npx -y yaver-cli
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add yaver-io-yaver --command npx --arg -y --arg yaver-cli
```

### Hermes

```yaml
mcp_servers:
  yaver-io-yaver:
    command: "npx"
    args: ["-y", "yaver-cli"]
```

### Other

```json
{
  "mcpServers": {
    "yaver-io-yaver": {
      "command": "npx",
      "args": [
        "-y",
        "yaver-cli"
      ]
    }
  }
}
```

## 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-03 (score 26, −3)

- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Package version: 1.99.396 → 1.99.398

### 2026-08-02 (score 29, 0)

- [security] Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.
- [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] 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] Capabilities: Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.

### 2026-08-01 (score 29, +15)

- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 1.99.390 → 1.99.396
- [functional] Package version: 1.99.390 → 1.99.395

### 2026-07-31 (score 14, −2)

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

### 2026-07-30 (score 16, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-28 (score 34, +18)

- [security improvement] Malware scan: 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] Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.

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

First indexed and scored.

## 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/yaver-io-yaver/yaver-cli#diagnostics

## Score history

- 2026-08-03: 26
- 2026-08-02: 29
- 2026-08-01: 29
- 2026-07-31: 14
- 2026-07-30: 16
- 2026-07-28: 34
- 2026-07-27: 16

## Links

- npm package: https://www.npmjs.com/package/yaver-cli
- Socket report: https://socket.dev/npm/package/yaver-cli
- Website: https://yaver.io/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/yaver-io-yaver/yaver-cli/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/yaver-io-yaver/yaver-cli/changelog.json
- HTML version of this page: https://verifymcp.io/servers/yaver-io-yaver/yaver-cli