
validar-semver
io.github.encodiPublished by GitHub account encodiv1.0.1Updated Sep 30, 2026
Resolves real semver range satisfaction (^1.2.3, ~2.0) against a version. Paid via x402/USDC.
Overview
A remote MCP server with one tool that checks whether a version satisfies a list of semver ranges, using the same engine npm uses.
- What you can do
- Evaluate a version against one or more semver ranges (caret, tilde, x-ranges, comparators) and get a real match result rather than a model guess.
- When to use it
- Useful when an assistant needs a trustworthy answer about whether a version satisfies a range, for example when reasoning about dependency constraints or release compatibility.
- Requirements
- Remote endpoint over streamable HTTP; no local runtime, account or API key is declared. Each call is billed and must be paid in USDC on Base mainnet, so a client able to make x402 payments is needed.
Installation
In SourceWeft
- Open validar-semver in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.encodi%2Fvalidar-semver/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"validar-semver": {
"type": "http",
"url": "https://validar-semver.encodari.workers.dev/mcp"
}
}
}README
validar-semver
Remote MCP server (Cloudflare Workers) with one tool that resolves real semver range satisfaction:
validate_semver— evaluates a version (e.g.1.2.3) against a list of ranges (^1.2.3,~2.0,2.x,>=1.0.0 <2.0.0, ...) using the same semver engine npm uses (semver), not a model guess about what should match.
No database, no persistent state: each call builds a fresh McpServer (see createServer() in src/index.ts) and is self-contained.
Billing (x402)
Charges per call via x402 — real USDC payment on Base mainnet, against the Coinbase Developer Platform (CDP) facilitator. The payment travels inside the MCP JSON-RPC itself (_meta), not as an HTTP header; see src/payments.ts.
An unpaid tools/call returns isError: true with the accepts (network, amount, payTo) the client needs to pay and retry — not an unexplained exception.
Structure
Running it locally
⚠️ Note on wrangler dev: the real Cloudflare Workers runtime (workerd) requires macOS 13.5+. If your Mac has an older version, wrangler dev (and npm run dev) will fail. This project includes a plain-Node shim that runs the exact same fetch() handler without needing workerd.
1. Install dependencies
2. Run the unit tests
3a. If your wrangler dev works (macOS 13.5+, Linux, Windows)
3b. If wrangler dev fails because of the macOS version
Starts at http://localhost:8787/mcp, reading CDP credentials from ~/.mcp-tools-factory-credentials.env (shared across all tools in this factory).
4. Test with curl
Responses come as Server-Sent Events (event: message + data: {...}); the data: line is the usual JSON-RPC response.
Deploy and listings
Deployed at https://validar-semver.encodari.workers.dev/mcp (Cloudflare Workers). Published on the official MCP registry, Smithery, mcp.so, and with an open PR to awesome-mcp-servers.
What it doesn't do (yet)
- Charges on Base mainnet with real money. To switch back to testnet (Base Sepolia,
eip155:84532) during development, changeNETWORKinsrc/payments.ts. - No database or persistent state between calls (beyond the billing config, cached in memory per isolate — see
src/payments.ts).
Source: README.md at commit cba3724
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts