io.github.mcurmi05/vdiff-mcp
NPM · VDIFF-MCP · SCANNED AUG 3
Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes.
Available components
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. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · vdiff-mcp
claude mcp add mcurmi05-vdiff-mcp -- npx -y vdiff-mcp
codex mcp add mcurmi05-vdiff-mcp -- npx -y vdiff-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mcurmi05-vdiff-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"vdiff-mcp"
],
"enabled": true
}
}
} openclaw mcp add mcurmi05-vdiff-mcp --command npx --arg -y --arg vdiff-mcp
mcp_servers:
mcurmi05-vdiff-mcp:
command: "npx"
args: ["-y", "vdiff-mcp"] {
"mcpServers": {
"mcurmi05-vdiff-mcp": {
"command": "npx",
"args": [
"-y",
"vdiff-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +39
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 1 Aug 26 +21
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −41
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
get_breaking_changes Get breaking changes between package versions ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
resolve_package Resolve npm package version ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | npm package name, e.g. "zod" or "@scope/pkg" |
No output schema declared.
No examples provided.