A
licenseNot graded
qualityB
maintenanceParse, validate, and explain cron expressions with pay-per-call via x402 (USDC on Base L2), returning next run times in any timezone.
1
MIT
validar-semver
Server Details
Resolves real semver range satisfaction (^1.2.3, ~2.0) against a version. Paid via x402/USDC.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- encodi/validar-semver
- GitHub Stars
- 0
- Server Listing
- validar-semver
Tool Definition Quality
A4.6/5.0
Tool DescriptionsA
Average 4.7/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of ambiguity or misselection. The tool's purpose is clearly stated.
Naming Consistency5/5
The single tool name 'validate_semver' follows the verb_noun pattern consistently. There are no other tools to create inconsistencies.
Tool Count3/5
With only one tool, the server feels minimal but appropriate for a very narrow purpose. The count is on the low end of borderline, but not excessive or trivial for a focused validator.
Completeness5/5
The tool fully covers semver validation, which is the entire stated domain. No obvious gaps exist for this specific purpose.
Available Tools
1 toolvalidate_semverValidate semver rangesAInspect
Resolves real semver range satisfaction (e.g. "^1.2.3", "~2.0", "2.x", ">=1.0.0 <2.0.0") against a version, using the same semver engine npm uses (the "semver" package), not a model guess about what should match. Costs $0.01 USDC (Base) per call.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ranges | Yes | List of semver ranges to evaluate against the version, one by one. Max 50 ranges, 256 characters each. | |
| version | Yes | The semver version to evaluate (e.g. "1.2.3", "1.2.3-beta.1", "v2.0.0"). | |
| include_prereleases | No | If true, allows a prerelease version (e.g. 1.3.0-beta.1) to match ranges that don't explicitly mention that same major.minor.patch tuple as a prerelease. Defaults to false (standard npm/semver behavior). |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| error | Yes | Error message if valid_version is false; null if valid. |
| results | Yes | One result per range, in the same order they were received. |
| valid_version | Yes | false if `version` isn't a valid semver. |
| normalized_version | Yes | Normalized form of `version` (e.g. "v1.2.3" -> "1.2.3"). null if valid_version is false. |
Tool Definition Quality
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly discloses that it uses the npm 'semver' package (not a heuristic), and mentions the cost of '$0.01 USDC (Base) per call'. These are meaningful behavioral details beyond the schema, providing transparency about execution and pricing.
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 sentences with no filler. It opens with the core action, provides illustrative examples compactly, and ends with a cost note. Every sentence earns its place and the structure is front-loaded.
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?
Given that the tool has a rich input schema (100% param coverage) and an output schema (not shown but present), the description only needs to add missing context. It successfully does so by clarifying the authoritative engine (npm semver) and the cost per call. For a simple validation tool, this is complete and sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already covers 100% of parameters with descriptions, so the baseline is 3. The description adds value by providing examples of accepted range formats ('^1.2.3', '~2.0', '2.x', '>=1.0.0 <2.0.0') and reinforces that evaluation follows npm's real semver logic, which helps clarify the semantics of the 'ranges' parameter beyond the schema's generic phrasing.
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 function: 'Resolves real semver range satisfaction' against a version, with concrete examples of range syntax. It distinguishes itself from a 'model guess' by specifying it uses the npm semver engine, which is more specific than merely restating the tool name.
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 this tool: when accurate, npm-compatible semver evaluation is needed, as it uses 'the same semver engine npm uses' and is 'not a model guess'. However, it does not explicitly list alternative tools or state when not to use it, but with no sibling tools this is somewhat mitigated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
- AlicenseNot gradedqualityCmaintenanceValidates regex, cron, and SQL expressions by executing them in real runtimes, with payments via x402 USDC on Base.MIT
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools to check a package's maintenance status, licence, and security advisories before you depend on it, with per-call payment in USDC on Base mainnet via x402.MIT
- FlicenseNot gradedqualityCmaintenanceProvides counterparty risk checks for any EVM address, returning malicious-history flags, tiered risk scoring, and plain-language summaries via x402 payment.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.