semver-checks
Related Servers
Alternatives to semver-checks
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables coding agents and developers to detect SemVer 2.0 breaking changes by statically diffing Python AST public API surfaces, catching removed exports, parameter reordering, and other incompatible signature shifts. It returns deterministic refactoring plans and dependency graph metrics without any external pip dependencies.7-
- FlicenseNot gradedqualityBmaintenanceEnables autonomous coding agents to audit source-code changes for SemVer 2.0 breaking changes by inspecting AST public API surface diffs, parameter reordering, and removed exports. Produces deterministic refactoring plans and dependency metrics using only the Python standard library.7-
- AlicenseNot gradedqualityCmaintenanceAnalyzes npm dependency upgrades to reveal which files and functions in your codebase break, with confidence tiers and transitive call chain tracing.5 npmMIT
- FlicenseNot gradedqualityBmaintenanceAnalyzes Git pull request diffs to detect breaking REST and GraphQL API schema changes, providing deterministic AST-level code review and breaking change alerts for CI/CD workflows.8-
- AlicenseAqualityCmaintenanceBreaking-change diffs for npm packages, served over REST and MCP, so coding agents stop writing code against outdated API knowledge.2Functional Source , Version 1.1, MIT Future
- AlicenseAqualityAmaintenanceTranslates a lockfile diff into a human-readable upgrade plan. For every dependency bump (npm or PyPI) returns semver class, breaking changes from GitHub release notes, CVEs fixed in the range, migration guide links, and a clear per-package recommendation. Bulk tool ranks up to 50 package changes in parallel by risk (security > caution > review > likely-safe > safe).2113 npm2MIT
TDQS
Scored across 2 tools
semver_compare and semver_snapshot have clearly distinct purposes: one diffs two versions to recommend or grade a SemVer bump, while the other only extracts an API surface. The descriptions explicitly direct agents to use snapshot for inspection and compare for bump decisions.
Both tools follow a consistent semver_<action> snake_case pattern. The names are predictable and directly reflect their operations.
Two tools is slightly thin against the typical 3-15 range, but this server has a narrow, well-defined purpose where both tools earn their place. No unrelated tools are present.
The core workflow is well covered: snapshot exposes the API surface, compare detects changes, recommends a bump, supports declared-version grading, and reports gate outcomes. Minor gaps may exist around CI integration or batch/multi-package workflows, but no obvious dead end for the stated purpose.