# io.github.mcurmi05/vdiff-mcp (npm · vdiff-mcp)

Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes.

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

## Components

- npm · `vdiff-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/mcurmi05-vdiff-mcp/vdiff-mcp.md), [page](https://verifymcp.io/servers/mcurmi05-vdiff-mcp/vdiff-mcp)

## Channel facts

- Registry: `npm`
- Package: `vdiff-mcp`
- Version: `0.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-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 31 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 314 tokens (~157/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add mcurmi05-vdiff-mcp -- npx -y vdiff-mcp
```

### Codex

```bash
codex mcp add mcurmi05-vdiff-mcp -- npx -y vdiff-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add mcurmi05-vdiff-mcp --command npx --arg -y --arg vdiff-mcp
```

### Hermes

```yaml
mcp_servers:
  mcurmi05-vdiff-mcp:
    command: "npx"
    args: ["-y", "vdiff-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "mcurmi05-vdiff-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "vdiff-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-02 (score 65, +39)

- [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: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional] Licence: MIT

### 2026-08-01 (score 26, +21)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 5, −41)

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

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

First indexed and scored.

## MCP tools (2)

### `resolve_package` (~66 tokens)

Resolve npm package version

Resolve an npm package to its latest published version and dist-tags. Use this when you only know the package name and need the current version, typically before calling get_breaking_changes.

Input parameters:

- `package` (string, required): npm package name, e.g. "zod" or "@scope/pkg"

### `get_breaking_changes` (~248 tokens)

Get breaking changes between package versions

Structured breaking-change diff between two versions of an npm package, computed from its TypeScript type declarations: removed exports, changed signatures, removed/changed class or interface members, plus new exports. Each entry has before/after signatures and a short migration note. The response includes a confidence score: 0.9 when both versions ship bundled types, 0.8 when DefinitelyTyped @types/* declarations were used. Use this before writing or upgrading code that targets a dependency version you are not certain about — e.g. when the installed version is newer than the API surface you know. The first request for a version pair may take up to a couple of minutes while the diff is computed; results are cached after that.

Input parameters:

- `from` (string, required): exact semver of the version you know or currently have installed, e.g. "3.24.0" (from a lockfile); ranges like "^3.0.0" are not accepted
- `package` (string, required): npm package name, e.g. "zod" or "@scope/pkg"
- `to` (string): exact semver of the version to compare against; omit to use the latest published version

## Diagnostics

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

## Score history

- 2026-08-03: 65
- 2026-08-02: 65
- 2026-08-01: 26
- 2026-07-31: 5
- 2026-07-30: 46
- 2026-07-28: 46
- 2026-07-27: 46

## Links

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