# io.github.DigiCatalyst-Systems/dep-diff-mcp (remote · dep-diff.digicatalyst.ca)

Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.

- Trust score: 85/100 (high trust)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `dep-diff.digicatalyst.ca`: 85/100 (this document), [markdown](https://verifymcp.io/servers/digicatalyst-systems-dep-diff-mcp/dep-diff.md), [page](https://verifymcp.io/servers/digicatalyst-systems-dep-diff-mcp/dep-diff)
- npm · `@digicatalyst/dep-diff-mcp`: 95/100, [markdown](https://verifymcp.io/servers/digicatalyst-systems-dep-diff-mcp/digicatalyst-dep-diff-mcp.md), [page](https://verifymcp.io/servers/digicatalyst-systems-dep-diff-mcp/digicatalyst-dep-diff-mcp)

## Channel facts

- Endpoint: `https://dep-diff.digicatalyst.ca/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 346 tokens (~173/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**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.DigiCatalyst-Systems/dep-diff-mcp server?

io.github.DigiCatalyst-Systems/dep-diff-mcp is a hosted endpoint at https://dep-diff.digicatalyst.ca/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http digicatalyst-systems-dep-diff-mcp 'https://dep-diff.digicatalyst.ca/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "digicatalyst-systems-dep-diff-mcp": {
      "url": "https://dep-diff.digicatalyst.ca/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "digicatalyst-systems-dep-diff-mcp": {
      "type": "http",
      "url": "https://dep-diff.digicatalyst.ca/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.digicatalyst-systems-dep-diff-mcp]
url = "https://dep-diff.digicatalyst.ca/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "digicatalyst-systems-dep-diff-mcp": {
      "type": "remote",
      "url": "https://dep-diff.digicatalyst.ca/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add digicatalyst-systems-dep-diff-mcp --url 'https://dep-diff.digicatalyst.ca/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  digicatalyst-systems-dep-diff-mcp:
    url: "https://dep-diff.digicatalyst.ca/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "digicatalyst-systems-dep-diff-mcp": {
      "Transport": "http",
      "Url": "https://dep-diff.digicatalyst.ca/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add digicatalyst-systems-dep-diff-mcp -t streamable-http -u 'https://dep-diff.digicatalyst.ca/mcp'
```

### Other

```json
{
  "mcpServers": {
    "digicatalyst-systems-dep-diff-mcp": {
      "type": "http",
      "url": "https://dep-diff.digicatalyst.ca/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-19 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 83, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-09-13 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `analyze_package_change` (~227 tokens)

Analyze a single dependency version change

Given one package and two versions (from -> to), returns a structured upgrade analysis: semver classification, GitHub release notes summary, detected breaking changes, security advisories fixed in the range, migration guide links, and a clear recommendation. Use when the user asks about a specific package upgrade ('what changed between react 18 and 19', 'is it safe to bump axios from 0.27 to 1.0', 'what does upgrading lodash 4.17.20 to 4.17.21 fix'). Supports npm, pypi, and github-actions (use the action reference as the name, e.g. actions/checkout). For analyzing many packages at once or a Dependabot batch, use analyze_packages_bulk instead.

Input parameters:

- `ecosystem` (string, required): Package ecosystem
- `fromVersion` (string, required): Current version (e.g. '18.2.0')
- `name` (string, required): Package name (e.g. 'react', 'requests')
- `toVersion` (string, required): Target version (e.g. '19.0.0')

Output parameters:

- `breakingChanges` (array): Breaking changes extracted from release notes; empty when none were found
- `ecosystem` (string): Package ecosystem
- `fromVersion` (string): Version being upgraded from
- `migrationLinks` (array): Migration or upgrade guide URLs found in release notes
- `package` (string): Package name that was analyzed
- `recommendation` (string): Single-line verdict explaining the recommendation level
- `recommendationLevel` (string): Risk classification, used to rank packages in bulk results
- `releaseCount` (number): Number of GitHub releases found strictly between the two versions
- `releaseExcerpts` (array): Raw release-note excerpts, present only as a fallback when a major/minor bump yielded no breaking changes
- `repoUrl` (string|null): Source repository URL, or null when none could be resolved
- `securityFixes` (array): Advisories affecting fromVersion that are resolved at toVersion
- `semverClass` (string): Semver relationship between the two versions
- `toVersion` (string): Version being upgraded to

### `analyze_packages_bulk` (~119 tokens)

Analyze multiple dependency changes in parallel

Analyzes a list of package upgrades in parallel and returns a unified risk report with packages ranked by recommendation level (security > caution > review > likely-safe > safe). Use when the user provides many dependency changes from a Dependabot PR, npm outdated output, lockfile diff, or batch upgrade. Returns: total count, breakdown by semver class, total security fixes found, packages with breaking changes, and per-package details. Limit 50 packages per call (chunk larger lists).

Input parameters:

- `changes` (array, required): List of package changes to analyze

Output parameters:

- `bySemverClass` (object): Breakdown of the batch by semver class
- `packages` (array): Per-package results, ranked security > caution > review > likely-safe > safe
- `packagesWithBreakingChanges` (number): How many packages had at least one breaking change
- `securityFixesTotal` (number): Total security advisories resolved across the whole batch
- `totalPackages` (number): Number of package changes submitted

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/digicatalyst-systems-dep-diff-mcp/dep-diff#diagnostics

## Score history

- 2026-09-20: 85
- 2026-09-19: 85
- 2026-09-18: 84
- 2026-09-17: 84
- 2026-09-16: 84
- 2026-09-15: 83
- 2026-09-14: 83
- 2026-09-13: 78
- 2026-09-12: 77
- 2026-09-11: 77
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 74
- 2026-09-03: 73
- 2026-09-02: 73
- 2026-09-01: 72
- 2026-08-31: 72
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 70
- 2026-08-26: 70
- 2026-08-25: 68
- 2026-08-24: 67

## Common questions

### What is the io.github.DigiCatalyst-Systems/dep-diff-mcp server?

io.github.DigiCatalyst-Systems/dep-diff-mcp is listed in the public MCP registry as io.github.DigiCatalyst-Systems/dep-diff-mcp. Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions. This page covers its hosted endpoint (https://dep-diff.digicatalyst.ca/mcp).

### Is the io.github.DigiCatalyst-Systems/dep-diff-mcp server safe to use?

io.github.DigiCatalyst-Systems/dep-diff-mcp scores 85 out of 100 on VerifyMCP. 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.DigiCatalyst-Systems/dep-diff-mcp server expose?

io.github.DigiCatalyst-Systems/dep-diff-mcp exposes 2 tools: analyze_package_change, analyze_packages_bulk. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.

### Does the io.github.DigiCatalyst-Systems/dep-diff-mcp server require authentication?

No. We connected to io.github.DigiCatalyst-Systems/dep-diff-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.DigiCatalyst-Systems/dep-diff-mcp server still maintained?

io.github.DigiCatalyst-Systems/dep-diff-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dep-diff.digicatalyst.ca/mcp
- Repository: https://github.com/DigiCatalyst-Systems/dep-diff-mcp
- Changelog RSS feed: https://verifymcp.io/servers/digicatalyst-systems-dep-diff-mcp/dep-diff.xml
- Changelog JSON feed: https://verifymcp.io/servers/digicatalyst-systems-dep-diff-mcp/dep-diff.json
- HTML version of this page: https://verifymcp.io/servers/digicatalyst-systems-dep-diff-mcp/dep-diff