Email Send API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 25, 2026

Send emails programmatically via Resend. Text and HTML. x402 micropayment.

VerifiedSSEWeb executableFinanceCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that lets an assistant send transactional emails through Resend, paid per call with USDC via the x402 protocol.

What you can do
Send an email message to one or more recipients, with a subject and a plain-text body or an HTML body that overrides it, and get back delivery confirmation with a message ID and status.
When to use it
Useful when an assistant needs to send transactional email such as notifications, alerts, password resets, order confirmations or automated reports without signing up for an email provider or managing an API key.
Requirements
A remote MCP endpoint added to the client configuration; no API key or signup. Payment requires an x402-capable client and a wallet holding USDC on Base L2 (eip155:8453); the client handles the 402 challenge, signing and retry. Network access to the endpoint is needed.
Before you install
Every send costs $0.008 in USDC from your wallet, so an assistant can spend funds on your behalf. Sending email is an outward action that cannot be recalled. The default sender is [email protected] unless you set your own from address. Message content is passed to the remote service and its payment facilitators.

Installation

In SourceWeft

  1. Open Email Send API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. 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.Br0ski777%2Femail-send/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "email-send-api": {
      "type": "sse",
      "url": "https://email-send.api.klymax402.com/mcp"
    }
  }
}

README

Email Send API

[MCP Server] [x402] [License: MIT]

Send emails programmatically via Resend -- text or HTML body, delivery status, message ID. Transactional email. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

json
{  "mcpServers": {    "email-send": {      "url": "https://email-send.api.klymax402.com/mcp"    }  }}

Quickstart -- HTTP (x402)

bash
curl -X POST "https://email-send.api.klymax402.com/api/send" \  -H "Content-Type: application/json" \  -d '{"to":"...","subject":"...","body":"..."}'# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
email_send_messagePOST/api/send$0.008Send an email message

email_send_message

Use this when you need to send an email to one or more recipients. Returns delivery confirmation in JSON.

Parameters

NameTypeRequiredDescription
tostringyesRecipient email address
fromstringnoSender email address (default: [email protected])
subjectstringyesEmail subject line
bodystringyesEmail body content (plain text)
htmlstringnoEmail body content (HTML, optional — overrides body)

Example response:

json
{"messageId":"msg_01abc123","status":"sent","timestamp":"2026-04-13T14:30:00Z","to":"[email protected]","from":"[email protected]","subject":"Your Report"}

When to use: sending transactional emails, notifications, alerts, password resets, order confirmations, and automated reports.

Not for: email validation (use email_verify_address), finding email addresses (use email_find_by_name), person data enrichment (use person_enrich_from_email).

Example agent prompts

  • "Send an email to one or more recipients"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Source: README.md at commit 736ac18

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 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