Ext Ops Panel
Open dashboard
Comparison

Resend vs x402 Email Verifier

Resend is an MCP server published by resend. 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-28. 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

Where each is published
MarketplaceResendx402 Email Verifier
Docker MCP Catalog Listed
Version: sha256:2a786579214e
Forks (GitHub): 91
Pulls (Docker Hub): 22 230
Stars (Docker Hub): 5
Stars (GitHub): 578
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

Resend vs x402 Email Verifier
FactResendx402 Email Verifier
Marketplaces that list it11
Stars (GitHub) (differs)578 (better)0 (worse)
Pulls (Docker Hub) (differs)22 230No figure on Docker Hub
Forks (GitHub) (differs)91 (better)0 (worse)
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (mcp/resend)Remote server (x402-email-verifier.microtools-x402.workers.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)3, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/resend/mcp-send-emailNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 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

Resend

In its own words, on Docker MCP Catalog:

The official MCP server to send emails and interact with Resend.

x402 Email Verifier

In its own words, on Official MCP Registry:

Email verification for AI agents: syntax, MX, disposable, role, score. $0.001 USDC/call via x402.

How to run each

Resend As a local MCP server: Docker image

Claude Code
claude mcp add --env "RESEND_API_KEY=<YOUR_RESEND_API_KEY>" --transport stdio resend -- docker run -i --rm -e RESEND_API_KEY mcp/resend

Requires: RESEND_API_KEY (secret)

x402 Email Verifier As a remote MCP server

Claude Code
claude mcp add --transport http email-verifier https://x402-email-verifier.microtools-x402.workers.dev/mcp

Commands 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 Resend has

  • send-email

Only x402 Email Verifier has

  • email_verify
  • health

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: Resend · 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.

Where the data comes from: how the catalog is built