io.github.DigiCatalyst-Systems/dep-diff-mcp
REMOTE · DEP-DIFF.DIGICATALYST.CA · 2 COMPONENTS · SCANNED SEP 20
Translates a lockfile diff into a human-readable upgrade plan for npm, PyPI, and GitHub Actions.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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.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.
remote · dep-diff.digicatalyst.ca
claude mcp add --transport http digicatalyst-systems-dep-diff-mcp 'https://dep-diff.digicatalyst.ca/mcp'
{
"mcpServers": {
"digicatalyst-systems-dep-diff-mcp": {
"url": "https://dep-diff.digicatalyst.ca/mcp"
}
}
} {
"servers": {
"digicatalyst-systems-dep-diff-mcp": {
"type": "http",
"url": "https://dep-diff.digicatalyst.ca/mcp"
}
}
} [mcp_servers.digicatalyst-systems-dep-diff-mcp] url = "https://dep-diff.digicatalyst.ca/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"digicatalyst-systems-dep-diff-mcp": {
"type": "remote",
"url": "https://dep-diff.digicatalyst.ca/mcp",
"enabled": true
}
}
} openclaw mcp add digicatalyst-systems-dep-diff-mcp --url 'https://dep-diff.digicatalyst.ca/mcp' --transport streamable-http
mcp_servers:
digicatalyst-systems-dep-diff-mcp:
url: "https://dep-diff.digicatalyst.ca/mcp" {
"McpServers": {
"digicatalyst-systems-dep-diff-mcp": {
"Transport": "http",
"Url": "https://dep-diff.digicatalyst.ca/mcp"
}
}
} assistant mcp add digicatalyst-systems-dep-diff-mcp -t streamable-http -u 'https://dep-diff.digicatalyst.ca/mcp'
{
"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.
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.
- 19 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +5
- HTTPS: unverified → pass ▲ security
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 4 Sept 26 +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.
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 20 Sept 2026 · Probed https://dep-diff.digicatalyst.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=digicatalyst.ca | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 10bc3d37c5ea4520e52d11322b486a3 |
| SANs: digicatalyst.ca, dep-diff.digicatalyst.ca, *.dep-diff.digicatalyst.ca | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dep-diff.digicatalyst.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| digicatalyst.ca. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dep-diff.digicatalyst.ca/mcp | Verified | 200 | |
| http (plaintext) | http://dep-diff.digicatalyst.ca/mcp | HTTPS enforced | 301 | https://dep-diff.digicatalyst.ca/mcp |
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 →
analyze_package_change Analyze a single dependency version change ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem |
| fromVersion | string | yes | Current version (e.g. '18.2.0') |
| name | string | yes | Package name (e.g. 'react', 'requests') |
| toVersion | string | yes | Target version (e.g. '19.0.0') |
| Name | Type | Req | Description |
|---|---|---|---|
| breakingChanges | array | yes | Breaking changes extracted from release notes; empty when none were found |
| ecosystem | string | yes | Package ecosystem |
| fromVersion | string | yes | Version being upgraded from |
| migrationLinks | array | yes | Migration or upgrade guide URLs found in release notes |
| package | string | yes | Package name that was analyzed |
| recommendation | string | yes | Single-line verdict explaining the recommendation level |
| recommendationLevel | string | yes | Risk classification, used to rank packages in bulk results |
| releaseCount | number | yes | 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 | yes | Source repository URL, or null when none could be resolved |
| securityFixes | array | yes | Advisories affecting fromVersion that are resolved at toVersion |
| semverClass | string | yes | Semver relationship between the two versions |
| toVersion | string | yes | Version being upgraded to |
No examples provided.
analyze_packages_bulk Analyze multiple dependency changes in parallel ~119
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).
| Name | Type | Req | Description |
|---|---|---|---|
| changes | array | yes | List of package changes to analyze |
| Name | Type | Req | Description |
|---|---|---|---|
| bySemverClass | object | yes | Breakdown of the batch by semver class |
| packages | array | yes | Per-package results, ranked security > caution > review > likely-safe > safe |
| packagesWithBreakingChanges | number | yes | How many packages had at least one breaking change |
| securityFixesTotal | number | yes | Total security advisories resolved across the whole batch |
| totalPackages | number | yes | Number of package changes submitted |
No examples provided.
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.