mcp server
BumpGuard
Reports which of your code's API usages break when you upgrade a dependency (Python, .NET, Java).
Description as published by the maintainer. Source
- version 0.2.1
- active
active — Most recent push to the repository was 2026-06-17.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 2 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-06-17 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.2.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-17 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-06-17 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
mendapi
— last commit 2026-08-05, shares breaking-changes
Detect API breaking changes, scan your codebase for impact, and draft the fix. Runs locally.
-
Delimit
— last commit 2026-07-28, shares breaking-changes
One workspace for every AI coding assistant. Shared tasks, memory, and governance.
-
Delimit — API Governance for AI Coding Assistants
— last commit 2026-07-28, shares breaking-changes
API governance for AI coding assistants. Breaking changes, policies, cross-model context.
-
OrangePro
— last commit 2026-08-05, shares static-analysis
Find test gaps, generate grounded tests, and dynamically prove behavior with mutation testing.
-
SkillsSafe Security Scanner
— last commit 2026-03-13, shares static-analysis
AI skill security scanner. Detects prompt injection, credential theft, ClawHavoc. Free, no signup.
-
Code Pathfinder
— last commit 2026-07-10, shares static-analysis
Code intelligence MCP server: call graphs, type inference, and symbol search for Python/Go.
-
Repowise
— last commit 2026-08-06, shares static-analysis
Codebase intelligence for AI coding agents — graph, git history, docs, decisions, code health.
-
io.github.aahlijia/dekko
— last commit 2026-08-06, shares static-analysis
Static code map generator: MAP.md + map.json for any repo, plus a Claude Code /map plugin
-
io.github.abhinavteja123/codemore
— last commit 2026-07-18, shares static-analysis
The static analyzer your AI agent reads — fix-ready, machine-readable scan reports over MCP.
-
pkgxray
— last commit 2026-08-06, shares static-analysis
Pre-install security scans for npm packages, MCP servers, and AI agents with cited verdict evidence.
These share tags the maintainers applied themselves, such as breaking-changes, static-analysis. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai, breaking-changes, dependencies, developer-tools, llm, mcp, model-context-protocol, python, static-analysis, upgrade.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab