Ext Ops Panel
Open dashboard
Comparison

dependency-evaluator vs io.github.DigiCatalyst-Systems/dep-diff-mcp

dependency-evaluator is a plugin bundle for AI coding tools published by apart-tech. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.DigiCatalyst-Systems/dep-diff-mcp is an MCP server published by DigiCatalyst-Systems. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacedependency-evaluatorio.github.DigiCatalyst-Systems/dep-diff-mcp
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.9
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 0.3.2
Downloads/month (npm): 402
Downloads/week (npm): 67
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

dependency-evaluator vs io.github.DigiCatalyst-Systems/dep-diff-mcp
Factdependency-evaluatorio.github.DigiCatalyst-Systems/dep-diff-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle11
LicenceMITMIT
Repository (differs)github.com/apart-tech/pluginsgithub.com/digicatalyst-systems/dep-diff-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

dependency-evaluator

In its own words, on Claude Code: claude-plugins-community:

Evaluate npm and Python packages before adding them as dependencies. Automatically gathers package metadata, analyzes source complexity, checks security and maintenance health, and produces a structured USE / EXTRACT / BUILD verdict. Auto-triggers when your agent is about to install a new package, or run on-demand with /evaluating-dependencies <package> [function]. Catches supply chain red flags like .pth injection, typosquatting, and stale maintainership.

io.github.DigiCatalyst-Systems/dep-diff-mcp

In its own words, on Official MCP Registry:

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

How to run each

dependency-evaluator

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.DigiCatalyst-Systems/dep-diff-mcp As a remote MCP server

Claude Code
claude mcp add --transport http dep-diff-mcp https://dep-diff.digicatalyst.ca/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: dependency-evaluator · What it can do: io.github.DigiCatalyst-Systems/dep-diff-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built