Validate semantic version ranges with npm's semver engine via an MCP server.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "validar-semver" yet — see the docs or source repo.
Please validate whether this semantic version range is valid: ^1.2.3 || ~2.0.0
Returns whether the version range is valid under semver rules.
Validate whether these dependency version ranges in package.json are valid: react: ">=18 <20", typescript: "~5.4.0"
Provides a validity check for each dependency version range.
Before release, check whether these version ranges are valid and flag any invalid entries: 1.x, latest, >=2.1.0 <3.0.0
Outputs valid and invalid ranges so they can be fixed before release.
Developers can use it while maintaining package.json or related configs to verify that version ranges follow semantic versioning rules and reduce dependency declaration errors.
DevOps or engineering teams can call this MCP tool in release or automation workflows to catch invalid semver ranges early.
It is an MCP server that uses npm's semver engine to validate whether semantic version ranges are valid.
The original description says it validates version ranges using npm's semver engine.
The original description mentions payment via x402 on Base mainnet. For configuration details, see the source repository.
Parse, compare, and validate semantic versions for releases and dependency decisions.
Verify AI-generated code for quality, security, and performance with more trust.
Validate AI-generated code with browser tests, evidence capture, and smart diagnostics.
Validate code rules, automate reviews, and generate reports across multiple stacks.
Map natural language to typed IDs and retrieve catalog and verification details.
Check MCP tool trust before installation and score stack risk.