VeyraX vs x402 Email Verifier
VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). x402 Email Verifier is an MCP server published by x402-email-verifier.microtools-x402.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  VeyraX | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:257d91533072 Forks (GitHub): 19 Pulls (Docker Hub): 18 771 Stars (Docker Hub): 4 Stars (GitHub): 48 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | VeyraX | x402 Email Verifier |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 48 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 18 771 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 19 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | On your machine (mcp/veyrax) | Remote server (x402-email-verifier.microtools-x402.workers.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/veyrax/veyrax-mcp | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-17 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
VeyraX
VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.
x402 Email Verifier
Email verification for AI agents: syntax, MX, disposable, role, score. $0.001 USDC/call via x402.
How to run each
VeyraX As a local MCP server: Docker image
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyraxRequires: VEYRAX_API_KEY (secret)
x402 Email Verifier As a remote MCP server
claude mcp add --transport http email-verifier https://x402-email-verifier.microtools-x402.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only x402 Email Verifier has a remote endpoint we check. How we check endpoints
Tools each declares
Only VeyraX has
get_flowget_toolstool_call
Only x402 Email Verifier has
email_verifyhealth
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (x402 Email Verifier as of 2026-10-23). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of x402 Email Verifier publish no settings it asks for, so we do not compare settings.
What it can do: VeyraX · What it can do: x402 Email Verifier · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.