io.github.tasuyoapp-ctrl/email-preflight·Messaging

Email Preflight

x402 v2 payment requests; relays compatible clients' signed payments to the existing product API.

Stars
—
Version
0.3.0
License
—
Review
Passed
Registry update
Oct 16, 2026

Connect

remote
Terminal
$claude mcp add --transport http email-preflight https://email-preflight-mcp.onrender.com/mcp

Headers

Nothing to configure — it works as is.

Security review

Review passed

Reviewed 12m ago.

tools
1 tools scanned
metadata
scanned

No findings.

Tools

1
  • email_preflight

    Use before sending or processing an email when you need current preflight facts about the address. For $0.001 USDC on Base mainnet, the existing Email Preflight API checks six facts: syntax validity, domain availability, MX availability, disposable-email detection, role-account detection, and free-provider detection. Example paid result shape: { email: "[email protected]", syntax: "valid", domain: "exists", mx: "found", disposable: "not_listed", role_based: "not_detected", free_provider: "not_detected" }. MX records do not prove that a mailbox exists. Unpaid requests return the original upstream HTTP 402 challenge. A compatible x402 client may retry with its own signed PaymentPayload in params._meta["x402/payment"]. This adapter never signs, owns a wallet, or settles independently.

More in Messaging

Listing from the official MCP Registry.