How does payment work?
Each API call is paid with USDC on Base. Costs are fixed per action (e.g., send email: $0.005, list messages: $0.002). $1 USDC covers approximately 200 emails.
@MuzsaiLajos
基本信息
Python SDK for x402mail - send and receive email with USDC micropayments
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"x402mail": {
"command": "x402mail",
"args": [
"mcp"
],
"env": {
"CDP_API_KEY_ID": "your-key-id",
"CDP_API_KEY_SECRET": "your-key-secret",
"CDP_WALLET_SECRET": "your-wallet-secret"
}
}
}
}工具列表暂未提供
当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。
工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。
X402mail is an email API that lets you send and receive emails with crypto micropayments. It requires no accounts or API keys—just a wallet. Built on the x402 protocol, every API call is paid with USDC on Base.
Install the package with pip install x402mail[cdp] (or pip install x402mail for private key usage). Set environment variables for your CDP wallet or provide an EVM private key. Use the Python API to send/receive emails, or run a local MCP server with x402mail mcp for AI agent integration.
Each API call is paid with USDC on Base. Costs are fixed per action (e.g., send email: $0.005, list messages: $0.002). $1 USDC covers approximately 200 emails.
The recommended setup is a Coinbase Developer Platform (CDP) Server Wallet, which requires CDP API keys. You can also use any EVM wallet with USDC on Base by providing a private key.
No. X402mail does not require traditional API keys. For CDP wallet usage, you need CDP API credentials (key ID, secret, wallet secret). For private key usage, you only need an EVM private key.
Send email: $0.005, check inbox: $0.001, list messages: $0.002, read message: $0.001. All costs are fixed in USDC on Base.
Yes. Run `x402mail mcp` to start a local MCP server. It provides tools like `send_email`, `get_inbox`, `list_messages`, and `read_message`. Configure it in your MCP client (e.g., Claude Desktop, Cursor) using the provided JSON block.

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools

Catch intent conflicts before code conflicts. The open-source coordination protocol for coding agents, built above Git.

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

The tools your AI needs to make your games. Turn prompts into production-ready game assets — animated characters with their weapons attached, seamless textures, terrain, VFX, HUDs — and playable game kits Unity, Godot, U
评论