F
license-
qualityC
maintenanceValidates regex, cron, and SQL expressions by executing them in real runtimes, with payments via x402 USDC on Base.
validar-semver
Server Details
Resuelve satisfaccion real de rangos semver (^1.2.3, ~2.0) contra una version. Pago x402/USDC.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- encodi/validar-semver
- GitHub Stars
- 0
- Server Listing
- validar-semver
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.3/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlapping purposes. The tool's purpose is clearly to validate semver ranges against a version.
Naming Consistency5/5
The single tool uses a clear snake_case verb_noun pattern ('validar_semver'), which is consistent and predictable. There are no other tools to create inconsistency.
Tool Count3/5
A single tool is borderline and feels thin, but it is appropriate for the narrow scope of semver validation. The server has exactly one focused capability, which is reasonable but not a typical well-scoped set.
Completeness5/5
The tool fully covers the domain of semver range satisfaction checking, the core and only intended purpose of the server. There are no obvious missing operations for this narrow scope.
Available Tools
1 toolvalidar_semverValidar rangos semverAInspect
Resuelve satisfacción real de rangos semver (ej: "^1.2.3", "~2.0", "2.x", ">=1.0.0 <2.0.0") contra una versión, usando el mismo motor semver que usa npm (paquete "semver"), no una suposición del modelo sobre qué debería matchear. Cuesta $0.01 USDC (Base) por llamada.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ranges | Yes | Lista de rangos semver a evaluar contra la versión, uno por uno. Máximo 50 rangos, 256 caracteres cada uno. | |
| version | Yes | La versión semver a evaluar (ej: "1.2.3", "1.2.3-beta.1", "v2.0.0"). | |
| include_prereleases | No | Si true, permite que una versión pre-release (ej: 1.3.0-beta.1) matchee rangos que no mencionan explícitamente esa misma tupla major.minor.patch en pre-release. Default false (comportamiento estándar de npm/semver). |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| error | Yes | Mensaje de error si valid_version es false; null si es válida. |
| results | Yes | Un resultado por cada range, en el mismo orden en que se recibieron. |
| valid_version | Yes | false si `version` no es un semver válido. |
| normalized_version | Yes | Forma normalizada de `version` (ej: "v1.2.3" -> "1.2.3"). null si valid_version es false. |
Tool Definition Quality
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the full burden. It discloses that it uses the real npm semver package (not a model guess) and mentions the $0.01 USDC cost per call. This adds meaningful behavioral context beyond the bare operation, though it does not mention error handling or response format (but output schema exists).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences. It front-loads the purpose, then differentiates from a naive model implementation, and finally states the cost. Every word earns its place, with no redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple, the schema is fully described, and an output schema exists. The description supplies the core value proposition (real npm semver), the exact inputs in context, and the cost, making it complete for an agent to understand what the tool does and its practical implications.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, so the baseline is 3. The description provides illustrative range examples but does not add extra semantics beyond what the schema already documents for parameters like include_prereleases. It meets the baseline but does not exceed it.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: resolving semver range satisfaction against a version using the official npm semver engine. It includes concrete examples of range formats and distinguishes itself from a model's guess, making the action and resource unmistakable.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool: when accurate, npm-equivalent semver matching is needed, rather than relying on an LLM's assumptions. It does not explicitly list exclusions or alternative tools, but there are no siblings, and the context is clear enough for an agent to decide.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityBmaintenanceParse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.1MIT
- Alicense-qualityBmaintenanceChecks token contract safety for honeypot, tax, proxy, blacklist, ownership risks, and returns a risk score, enabling rug-pull protection for agents via pay-per-call x402 micropayments.MIT
- Flicense-qualityCmaintenanceProvides counterparty risk checks for any EVM address, returning malicious-history flags, tiered risk scoring, and plain-language summaries via x402 payment.
Try in Browser
Your Connectors
Sign in to create a connector for this server.