MCP.Market

smails MCP server

online · 100% uptime
by pexni·io.github.pexni/smails·v0.1.0·39 stars

Disposable email inboxes for AI agents: create an address, wait for the verification email.

A99/100grade A
What users say
No reviews yet
Be the first
Safety scan
A99/100

full report

Adoption
Established

39 stars301 downloads/wk

Reviews

Write one

Nobody has reviewed smails yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

smails tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-08 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • Live reliabilityremote reachable in 226ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 99/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How smails compares

Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
99/100
higher than 98% of 915 Email servers
Uptime
100%
of our recent checks; the typical remote Email server answers 100%
Response time
97 ms
faster than 81% of 609 Email servers
GitHub stars
39
more than 92% of 502 Email servers
Downloads a week
301
more than 74% of 270 Email servers with a package

Release history: 2 versions in the registry since 2026-06-26, latest 2026-11-05, typically one every 132 days.

Install smails in Claude Code, Cursor or VS Code

claude mcp add --transport http smails https://smails.dev/mcp
Add to Cursor

What the publisher says

From the smails repository's README, as published. We do not edit it. Read it on GitHub

smails

Disposable email for humans and AI agents. An instant, anonymous throwaway inbox for sign-ups, one-time codes, and confirmations — with a REST API, a CLI, and an MCP server, so your AI agent can receive verification emails too. No signup, no password.

→ smails.dev · npx @smails/cli create

Give your agent its own inbox: plug the MCP server into Claude, Cursor, or any MCP client and it can create a mailbox and read incoming mail (verification codes, magic links) on its own.

Features

  • Instant inbox — open the site and you have an address, zero clicks
  • Real-time — new mail arrives over WebSocket, no polling
  • Built for agents — REST API, CLI, and an MCP server share the same mailbox
  • Multi-domain — pick from configurable receiving domains
  • Self-cleaning — mailboxes auto-expire after 7 days of inactivity
  • Serverless — Cloudflare Workers + Durable Objects (one DO per mailbox, SQLite storage)

Quick start

Web

Visit smails.dev — an inbox is created for you on first load.

CLI

npx @smails/cli create      # create a mailbox (token saved to ~/.smails)
npx @smails/cli inbox       # list messages
npx @smails/cli read <id>   # read a message (id prefix is enough)
npx @smails/cli whoami      # show the current address
npx @smails/cli create --force  # replace with a fresh mailbox

MCP (for AI agents)

Add the server to any MCP client (e.g. Claude Desktop, ~/.claude/mcp.json):

{
  "mcpServers": {
    "smails": { "command": "npx", "args": ["@smails/cli", "mcp"] }
  }
}

Tools: createmailbox, listmessages, readmessage, deletemessage, get_address.

REST API

# create a mailbox
curl -X POST https://smails.dev/api/mailbox
# → { "address": "...", "token": "..." }

# list messages with the returned token
curl https://smails.dev/api/mailbox/messages \
  -H "Authorization: Bearer <token>"

Authenticate every request (except create) with Authorization: Bearer .

How it works

Inbound mail ──▶ Cloudflare Email Routing (catch-all)
                          │
                          ▼
                  Worker  email() handler ──┐
                                            ▼
   Web / CLI / MCP ──REST + WS──▶  Durable Object  (one per mailbox)
                                   ├─ SQLite (messages)
                                   ├─ token auth
                                   └─ 7-day alarm → cleanup
  • Each mailbox is a single Durable Object, addressed by its name; messages live in the DO's SQLite.
  • The token is {address}.{secret}; the Worker routes by address, the DO verifies the full token.
  • A 7-day alarm wipes inactive mailboxes; any activity renews it.

Project structure

frontend/   React Router SPA (prerendered) — Tailwind v4 + shadcn
worker/     Cloudflare Worker + Durable Objects — Hono routing, postal-mime parsing
cli/        npm package — CLI + MCP server (@smails/cli)

Development

Each package is independent (pnpm). Install per package.

# frontend
cd frontend && pnpm install && pnpm dev

# worker (API + Durable Objects)
cd worker && pnpm install && pnpm dev

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-08restoreB → Ascore 99

smails: common questions

Is smails MCP server safe?
Yes, by our scan: it is graded A (99/100). Read the smails safety report
How do I install smails?
It runs remotely at smails.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does smails need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is smails maintained?
The last commit was 10 days ago (2026-11-05). The latest release is v0.1.0.
Is smails up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of smails?
Servers from other publishers that do the same job: SMTPing Email Verification MCP server, send0 MCP server and Postfleet MCP server. Compare all smails alternatives.
How does smails compare with other Email MCP servers?
safety score 99/100 (higher than 98% of 915 Email servers); uptime 100% (of our recent checks; the typical remote Email server answers 100%); response time 97 ms (faster than 81% of 609 Email servers). Full comparison.

Alternatives to smails

Same job from other publishers: the closest match first, then the best rated.

All smails alternatives →
  • SMTPing Email Verification
    Verify email addresses, clean lists and check spamtrap, disposable, spambot and complainer lists.
    A
  • send0
    Email inboxes for AI agents: create an address, wait for codes and links, send and reply in threads.
    A
  • Postfleet
    Give an AI agent its own email address: send, reply, read, and wait for mail.
    A
  • ZeroDrop
    Disposable email inboxes for AI agents — OTPs and magic links auto-extracted. No signup to try.
    B
  • e2a — email for AI agents
    Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
    A