Ext Ops Panel
Open dashboard
Comparison

BumpGuard vs io.github.white-hat-lab/safe-upgrade

BumpGuard is an MCP server published by appcreationsca. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.white-hat-lab/safe-upgrade is an MCP server published by white-hat-lab. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
MarketplaceBumpGuardio.github.white-hat-lab/safe-upgrade
Official MCP Registry Listed
Version: 0.2.1
Downloads/month (PyPI): 167
Downloads/week (PyPI): 37
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 0.2.0
Downloads/month (npm): 128
Downloads/week (npm): 19
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

BumpGuard vs io.github.white-hat-lab/safe-upgrade
FactBumpGuardio.github.white-hat-lab/safe-upgrade
Marketplaces that list it11
Stars (GitHub) (differs)5No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (bumpguard-mcp)On your machine (safe-upgrade-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/appcreationsca/bumpguard-mcpgithub.com/white-hat-lab/x402-safe-upgrade-api
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

BumpGuard

In its own words, on Official MCP Registry:

Reports which of your code's API usages break when you upgrade a dependency (Python, .NET, Java).

io.github.white-hat-lab/safe-upgrade

In its own words, on Official MCP Registry:

Evidence-backed npm upgrade preflight and dependency audits for coding agents, paid via x402.

How to run each

BumpGuard As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio bumpguard -- uvx bumpguard-mcp

io.github.white-hat-lab/safe-upgrade As a local MCP server: npm package

Claude Code
claude mcp add --env "PAYER_PRIVATE_KEY=<YOUR_PAYER_PRIVATE_KEY>" --transport stdio safe-upgrade -- npx -y safe-upgrade-mcp

Requires: PAYER_PRIVATE_KEY (secret)

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

The marketplaces of BumpGuard publish no settings it asks for, so we do not compare settings.

What it can do: BumpGuard · What it can do: io.github.white-hat-lab/safe-upgrade · Compare two other plugins

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