CryptoAgentMail
Give your agent a hosted inbox with send, receive, memory, and recovery so outreach, alerts, and human handoffs work without you building SMTP yourself.
Overview
CryptoAgentMail is a MCP server for the Build phase that provides hosted agent email with inboxes, send/receive, memory, recovery, and API-key access over HTTP.
What is this MCP server?
- Hosted streamable-http MCP at https://srun66.com/mcp with X-API-Key authentication
- Agent inboxes with send/receive, memory, and recovery flows
- Credit-based hosted service (CryptoAgentMail v0.4.0)
- Repository: influqa/crypto-agent-mail-skills on GitHub
- Registry version 0.4.0
- Remote endpoint https://srun66.com/mcp
- Required header X-API-Key
Community signal: 1 GitHub stars.
What problem does it solve?
Builders want agents that can read and send real email but do not want to run SMTP, deliverability, and inbox storage themselves.
Who is it for?
Solo builders shipping agent products that need quick, API-key hosted email for support, outreach, or autonomous workflows.
Skip if: Teams with strict data residency, fully self-hosted mail requirements, or products that need deep custom SMTP control without a third-party credits model.
What do I get? / Deliverables
Your agent gains a credited hosted mailbox pipeline you register once in MCP config instead of building mail infrastructure from scratch.
- Configured remote email MCP in the agent
- Working send/receive against agent inboxes
- Memory and recovery hooks for mail-backed workflows
Recommended MCP Servers
Journey fit
Email capability is added while you are assembling agent infrastructure in the product build phase. It extends what agents can do day-to-day (mailboxes and credits), which is core agent-tooling rather than frontend or docs work.
How it compares
Hosted communication MCP, not a local browser-research or DNS discovery server.
Common Questions / FAQ
Who is crypto-agent-mail for?
Indie builders and small teams adding real email inboxes to Claude Code, Cursor, Codex, or other MCP-capable agents via a hosted API.
When should I use crypto-agent-mail?
Use it in Build when your agent must send or receive email, retain mail-related memory, or recover mailbox state without self-hosting mail servers.
How do I add crypto-agent-mail to my agent?
Register the remote MCP URL https://srun66.com/mcp as streamable-http in your agent, and configure the secret header X-API-Key from CryptoAgentMail credits signup.