BumpGuard
Description
BumpGuard is an MCP server for pre-flight dependency-upgrade analysis: before you bump a dependency, it reports which of your usages break, with line numbers, severity, and fix hints. It also verifies AI-written code against installed APIs to catch hallucinations. Static…
About
BumpGuard is an MCP server for pre-flight dependency-upgrade analysis: before you bump a dependency, it reports which of your usages break, with line numbers, severity, and fix hints. It also verifies AI-written code against installed APIs to catch hallucinations. Static analysis only — never executes third-party…
Details
- Author
- appcreationsca
- Categories
- Developer Tools
Jump to
Setup
Install BumpGuard in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/appcreationsca/bumpguard-mcp
Follow the installation instructions in the repository README, then restart your MCP client.
Guard your dependency bumps.BumpGuard is aModel Context Protocol(MCP) server that tells your AI coding agentexactly which lines ofyourcode breakwhen you upgrade a dependency — and verifies AI‑written code against the API that isactually installed, so it stops calling functions that don't exist.
It does this bystatic analysis only. BumpGuard never imports or executes third‑party code; it reads a package's real public API straight from its source.
Docs tell your agent whatshouldexist. BumpGuard tells it whatactuallyexists here.
The #1 frustration developers report with AI coding tools is code that's"almost right, but not quite."A huge slice of that isAPI drift and hallucination:
- The model writespydantic.BaseSettingsoropenai.ChatCompletion.create(...)— perfectly valid two versions ago,gonein the version you have installed.
- You bumppandasfrom 1.5 to 2.2 and discover the breakage one stack trace at a time.
- A changelog lists1,800 breaking changes; you only care about thethreeyour code actually touches.
BumpGuard closes that gap with ground truth from your environment instead of the model's memory.
A real example — upgradingpydantic1 → 2 in code that usesBaseSettings:
// check_upgrade(package="pydantic", to_version="2.0.3", from_version="1.10.13", code="...") { "safe_to_upgrade": false, "summary": { "breaking": 1, "total_api_changes": 4919, "breaking_api_changes": 2015 }, "findings": [ { "symbol": "pydantic.BaseSettings", "line": 2, "severity": "breaking", "message": "You use 'pydantic.BaseSettings', which no longer exists in the target version...", "suggestion": "Consider 'pydantic.v1.env_settings.BaseSettings'" } ] }
Out of2,015breaking API changes, BumpGuard surfaced theonethat affects this code — with the line number and a fix hint.
Every answer is grounded in evidence (installed version, source location). Because analysis is static,"no findings" means "nothing proven to break," not a guarantee— BumpGuard is explicit about that in its output.
Requires Python 3.10+. The server speaks MCP over stdio.
Install BumpGuard into thesame environment as the project you're working on, so it sees the packages you actually have installed.
Claude Desktop / Claude Code(claude_desktop_config.json):
{ "mcpServers": { "bumpguard": { "command": "bumpguard-mcp" } } }
Cursor / Windsurf / VS Code (Copilot)— point your MCP config at thebumpguard-mcpcommand (orpython -m bumpguard.server). Any MCP‑compatible client works.
- "Before upgrading pandas to 2.2, check whether my data pipeline breaks."
- "Verify this snippet actually uses the installed OpenAI SDK."
- "List the real methods onhttpx.Client."
┌──────────────── language‑neutral core ────────────────┐ MCP tools → │ diff engine · breaking‑change classifier · analyzer │ │ (matches API changes against YOUR usage) │ └───────────────────────┬──────────────────────────────┘ │ Provider interface ┌───────────────────────┴──────────────────────────────┐ │ Python provider │ .NET (NuGet) │ Java (Maven) │ │ • AST surface │ • DLL metadata │ • jar bytecode │ │ • usage scanner │ • Roslyn scan │ • source scan │ │ • wheel fetch │ • nupkg fetch │ • jar fetch │ └──────────────────────────────────────────────────────┘
- Extracta package's public API surface by parsing its source with Python'sast— for the installed version, and for the target version (downloaded as a wheel and unpacked,never installed or executed).
- Diffthe two surfaces into removed / signature‑changed / added symbols, and classify each as breaking, potentially breaking, or info.
- Scanyour code (also viaast) for usages — resolving import aliases, re‑exports, instance‑method calls, and the keyword/positional arguments each call passes.
- Matchusages against changes and report a precise, per‑line verdict.
Safety:BumpGuard never imports third‑party code, so there are no import side effects, no hangs from heavy packages, and no arbitrary code execution. Wheel downloads are sandboxed to a temp dir, time‑bounded, and guarded against path traversal / zip bombs.
BumpGuard is built around apluggable provider interface. The diff engine, breaking‑change classifier, analyzer, reporting, and MCP tools are all language‑neutral; only thesurface extractionandusage scanningare ecosystem‑specific.
- ✅Python (PyPI)— available now.
- ✅.NET (NuGet)— available now. Reads public API from assembly metadata via reflection-only loading (no code executed); needs the.NET SDK(dotnet) on PATH. A small helper is built once on first use.
- ✅Java (Maven)— available now. Reads public API directly from compiled.jarbytecode (constant pool, access flags, descriptors) inpure Python—no JDK or Maven requiredand no third‑party code is executed.
- 🔜JS/TS (npm)— parse.d.tsdeclarations.
Adding an ecosystem means implementing oneProvider— seedocs/ADD_A_PROVIDER.md.
- Passlanguage: "dotnet". Example:"Before upgrading Azure.AI.OpenAI to 2.1.0, check whether my client code breaks (from_version 1.0.0-beta.17)."
- Supported:check_upgrade,diff_versions,list_symbols,check_import.
- Prefer passingfrom_version— the "installed" baseline is taken from the NuGet global cache, which isn't your project's pinned version.
- Reliable signal:type / method / property removals and additions(e.g. theOpenAIClient→AzureOpenAIClientrename is caught as a breaking removal with a suggestion). Parameter-level diffs run only forunambiguous single-overloadmembers; overloaded members are tracked by presence (a documented v1 limit).
- Fully-qualified references are reported confidently; short names resolved viausingare reported aslower-confidence "potentially breaking"to avoid false hard-breaks from namespace collisions.
- verify_snippetisnot supported for .NET in v1(accurate C# hallucination detection needs semantic binding).
- Passlanguage: "java"and identify packages by their Mavencoordinategroup:artifact(e.g.com.google.code.gson:gson). Example:"Before upgrading com.google.code.gson:gson to 2.10.1, check whether my code breaks (from_version 2.8.9)."
- Supported:check_upgrade,diff_versions,list_symbols,check_import.
- The public API surface is readdirectly from.jarbytecode(the jar is a zip of.classfiles; BumpGuard parses the class‑file structure withstruct— reading metadata, never running it). The target jar is fetched fromMaven Central(sandboxed, size‑capped, time‑bounded).No JDK/Maven needed.
- Prefer passingfrom_version— the "installed" baseline is read from your local~/.m2cache, which may not match your project's pinned version.
- Reliable signal:type / method / field / constructor removals and additions, and arity changes. Fully-qualified references hard-break; short names resolved viaimportare reported aslower-confidence "potentially breaking"to avoid false hard-breaks from namespace collisions.
- Documented v1 limits: generics areerasedin bytecode descriptors (so generic type-argument changes aren't seen);return-type-onlychanges andvarargs removalare tracked conservatively;overloadedmembers are tracked by presence (per-overload removal isn't detected); multi-release jars use the highest version overlay. The source usage scanner is a robust heuristic, not a full parser — it can pick up a name's owndeclarationorimportline as a reference, but these resolve to unqualified names that are capped at"potentially breaking"and can never produce a false hard-break.verify_snippetisnot supported for Java in v1(accurate hallucination detection needs semantic binding).
BumpGuard is honest about static analysis. It maymiss(false negatives) or, rarely,over‑flag(false positives):
- Dynamically generated APIs (__getattr__modules, plugin registries,boto3‑style clients). BumpGuard detects__getattr__modules andsuppressesconfident "missing symbol" findings under them.
- Members created at runtime that aren't visible in source.
- Compiled (C/Rust) extension internals — the Python‑level surface is still read.
- Deep instance‑flow tracking is limited to directx = Class(...)patterns.
- Star re‑exports (from .x import *) are not expanded.
Treat findings ashigh‑signal guidance, and absence of findings as "not proven unsafe," not a guarantee.
git clone https://github.com/appcreationsca/bumpguard-mcp cd bumpguard-mcp python -m venv .venv && . .venv/Scripts/activate # Windows pip install -e ".[dev]" pytest
The test suite (42 tests) runs offline using fixture packages — no network required.
Releases are automated via GitHub Actions. To cut a release:
- Bump the version inpyproject.tomlandsrc/bumpguard/__init__.py.
- Move theCHANGELOG.md"Unreleased" notes under a new version heading.
- Commit, then tag and push:
TheReleaseworkflow runs the tests, builds the wheel + sdist, and publishes to PyPI viaTrusted Publishing(OIDC — no stored tokens). TheCIworkflow runs the test matrix (Linux + Windows, Python 3.10/3.13) on every push and PR.
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Boost security in your dev lifecycle via SAST, SCA, Secrets & IaC scanning with Cycode.
Enable AI agents to secure code with Semgrep.
Skene is a codebase analysis toolkit for product-led growth. It scan your codebase, detect growth opportunities, and generate actionable implementation plans.
Provides seamless integration with SonarQube Server or Cloud, and enables analysis of code snippets directly within the agent context
AI-to-AI code review platform — Claude, Codex, and Gemini cross-check each other via MCP, REST API, and CLI for consensus-based results.
A stateful LSP runtime for AI agents: warm language server sessions with 50+ tools for go-to-definition, find-references, diagnostics, rename, and more across 30+ languages.
Persistent code index using Tree-sitter for fast, precise code search. Replaces grep with ~50 token responses instead of 2000+.
AI-powered code quality analysis to detect best practice violations, security issues, and architectural problems in real-time.
Orchestrates a dual-AI engineering loop where a Primary AI plans and implements, while a Review AI validates and reviews, with continuous feedback for optimal code quality. Supports custom AI pairing (Claude, Codex, Gemini, etc.)
AmazingMCP — MCP Server for .NET / C# Codebases
An MCP server that gives AI agents deep understanding of C# codebases via Roslyn — type search, dependency graphs, usage analysis, and architecture overviews, all from a live in-memory compilation.
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





