Skip to main content
Glama
518,816 tools. Updated 2026-09-06 06:38

"SemVer" matching MCP tools:

  • Compare two OpenAPI specs to detect breaking changes and policy violations, returning a pass/fail verdict for CI merge gates.
    MIT
  • Publish a new npm package version by bumping semver, packing, and pushing to the registry after required deploy gates, with dry-run support.
    MIT
  • Generate a shareable API diff report with full analysis, including diff, policy checks, semver impact, spec health, and migration guide. Ideal for API reviews, PR comments, and compliance records.
    MIT
  • Determine the semver bump (MAJOR/MINOR/PATCH/NONE) from API spec changes, and optionally compute the next version string. Use it when you need a deterministic release-version decision before merging a spec change.
    MIT

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Provides semantic versioning tools to parse, compare, and check range satisfaction for version strings, enabling version management through natural language queries.
    8
    MIT

Matching MCP Connectors

  • Semantic Versioning (semver) MCP.

  • Resolves real semver range satisfaction (^1.2.3, ~2.0) against a version. Paid via x402/USDC.

  • Returns a verified migration map with ordered breaking changes, before/after code, and source citations for upgrading a package between two versions.
    Business Source 1.1
  • Check compatibility of two package versions using curated peer dependency data from migration maps. Returns true, false, or unknown.
    Business Source 1.1
  • Stop a device's transport session to free its resources while keeping others running. Use to restart a stuck transport or end one session; on Chromium this also closes the CDP session, requiring a later reconnect.
    Apache 2.0
  • Analyze project-aware compatibility between two package versions to identify breaking changes and migration fixes.
    Business Source 1.1
  • Retrieve an agent's complete version history including semver tags, version and policy hashes, and deployment timelines to identify which policy version produced a specific track record. Responses are cryptographically verified.
    MIT
  • Bump the SemVer version of a vault recipe or component note, update its frontmatter, and log history in a sidecar JSON. Use read-only mode to inspect without changes.
    MIT
  • Get verified breaking changes for upgrading a package version, with source citations and last verified dates. Only returns data from curated migration maps, not guesses.
    Business Source 1.1
  • Check the exact build of the running MCP server by displaying package.json version, git commit hash, and dirty-tree status. Use it to determine whether a server process is stale or current.
    MIT
  • Download or load a COMSES model from cache, resolve version, and open it in NetLogo workspace if compatible, or return structured metadata for other models.
    MIT
  • Publish new or updated Standard Operating Procedure (SOP) documents. Enforces lint rules so errors block publication, and auto-increments versions.
    Apache 2.0
  • List available audit engine versions with semver tags, 'latest' alias, and release notes. Use to pin specific versions for reproducible audit results or identify newer analyzers.
    MIT
  • Identify the version that fixes a specific vulnerability and the semver distance (major, minor, or patch) to that fix, helping assess upgrade effort before attempting it.
    Apache 2.0
  • Check the kObsidian server's package name, semver, host runtime, and runtime version to confirm the build or perform a health check. Read-only.
    Apache 2.0
  • Create structured skill entries, retrieve relevant ones by query, and log success outcomes to build a shared, reusable agent knowledge catalog.
    MIT
  • Compare two package versions to receive a structured upgrade analysis: semver classification, breaking changes, security advisories, migration guides, and a recommendation.
    MIT