io.github.mcurmi05/vdiff-mcp
NPM · VDIFF-MCP · SCANNED SEP 22
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. 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 81 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.mcurmi05/vdiff-mcp server?
io.github.mcurmi05/vdiff-mcp runs locally as an npm package, launched with npx -y vdiff-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · vdiff-mcp
claude mcp add mcurmi05-vdiff-mcp -- npx -y vdiff-mcp
{
"mcpServers": {
"mcurmi05-vdiff-mcp": {
"command": "npx",
"args": [
"-y",
"vdiff-mcp"
]
}
}
} {
"servers": {
"mcurmi05-vdiff-mcp": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"vdiff-mcp"
]
}
}
} assistant mcp add mcurmi05-vdiff-mcp -t stdio -c npx -a -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.
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/vdiff-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
What is the io.github.mcurmi05/vdiff-mcp server?
io.github.mcurmi05/vdiff-mcp is listed in the public MCP registry as io.github.mcurmi05/vdiff-mcp. Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes. This page covers its npm package (vdiff-mcp).
Is the io.github.mcurmi05/vdiff-mcp server safe to use?
io.github.mcurmi05/vdiff-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mcurmi05/vdiff-mcp server expose?
io.github.mcurmi05/vdiff-mcp exposes 2 tools: resolve_package, get_breaking_changes. Their descriptions and schemas cost roughly 314 tokens of context every time the server is loaded.
Is the io.github.mcurmi05/vdiff-mcp server still maintained?
io.github.mcurmi05/vdiff-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.mcurmi05/vdiff-mcp server under?
io.github.mcurmi05/vdiff-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.