MCP For Claude Marketplace
Semantic Versioning Checker

Semantic Versioning Checker MCP Connector for Claude

A+

A high-precision engine for validating and comparing Semantic Versioning 2.0.0 strings.

3 tools Official Updated Oct 1, 2026 Official Vinkius Partner
More Details Connect to Claude

This MCP server provides precise tools for working with Semantic Versioning 2.0.0. It allows AI agents to validate version strings using parse_version, determine precedence between two versions with compare_versions, or sort a list of versions using list_precedence_order. It strictly adheres to SemVer rules, including pre-release precedence and build metadata handling.

semverversioningvalidationcomparisonsoftware-development

3 tools expose this connector's capabilities to your AI agent.

list_precedence_order

Returns a sorted list of unique version strings based on SemVer precedence

compare_versions

0.0 rules. Build metadata is ignored. Determines the precedence relationship between two SemVer versions

parse_version

Validates a SemVer 2.0.0 string and extracts its components

See how to talk to your AI agent using Semantic Versioning Checker.

Is '1.0.0-beta.1' a valid SemVer string?

Yes, '1.0.0-beta.1' is a valid Semantic Versioning 2.0.0 string.

Which version is higher: 1.2.3 or 1.2.3-rc.1?

1.2.3 is higher than 1.2.3-rc.1.

Sort these versions: 2.0.0, 1.0.0, 1.0.0-alpha

1.0.0-alpha, 1.0.0, 2.0.0

Yes, `parse_version` extracts build metadata, though it is ignored during precedence comparisons as per the SemVer 2.0.0 specification.

Related Connectors

Git Merge Conflict Resolver

Git Merge Conflict Resolver MCP

3 tools Official

Automatically identify and resolve Git merge conflict markers using deterministic strategies.

A+ View details →
Task Completion Enforcer Prover

Task Completion Enforcer Prover MCP

1 tools Official

An AI was asked to build 5 API endpoints, write tests, and update documentation. It built 3 endpoints, left TODO comments in the tests, never touched the documentation, and declared 'Done! Let me know if you need anything else.' The user spent 40 minutes finding the gaps. This happens every single day, on every LLM, in every coding session. This tool forces five completion axes: requirement extraction, completion evidence, gap identification, continuation execution, and final verification against the original request.

A+ View details →
Log Line Key-Value Parser

Log Line Key-Value Parser MCP

3 tools Official

Extracts structured data and character offsets from unstructured log lines.

A+ View details →
NEW
Song Key Transposer

Song Key Transposer MCP

4 tools Official

Transposes chord sequences between musical keys with accidental preference.

A+ View details →