Mailsink MCP server
io.github.heocoi/mailsink·v0.1.5Disposable inboxes for AI agents and CI: catch the verification email, read the OTP or link.
0 stars39 downloads/wk
Reviews
Write oneNobody has reviewed Mailsink yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Mailsink tools (8, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
create_inboxwrite actionCreate a temporary email inbox. Returns the email address to use for signups/verification.
delete_inboxwrite actionDelete an inbox and all its messages.
get_messageGet the full content of a specific message.
get_verification_codeGet the most recent OTP/verification code from an inbox. Polls if no code found yet.
get_verification_linkGet the most recent verification/magic link from an inbox. Polls if no link found yet.
list_inboxesList all active (non-expired) inboxes.
list_messagesList all messages in an inbox.
wait_for_emailwrite actionWait for an email to arrive in an inbox. Polls until a message appears or timeout.
Public scan report
scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it
- Code scan3 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 73 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Mailsink compares
Against every graded Email MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 62% of 916 Email servers
- Tools
- 8
- the typical Email server has 7
- Tools that change things
- 38%
- typical: 25%. Fewer write tools means less an agent can break
- Downloads a week
- 39
- more than 25% of 235 Email servers with a package
What its tools let an agent do: 5 read · 1 create · 1 change · 1 delete
Install Mailsink in Claude Code, Cursor or VS Code
Runs npx -y @mailsink/mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add mailsink -- npx -y @mailsink/mcp
What the publisher says
From the Mailsink repository's README, as published. We do not edit it. Read it on GitHub
@mailsink/mcp
Model Context Protocol server for MailSink — programmatic temporary email inboxes for AI agents and test automation.
Gives your agent eight typed tools for provisioning disposable addresses, waiting on signup emails, extracting OTP codes and magic links, and cleaning up after itself. Works in Claude Code, Claude Desktop, Cursor, Windsurf, and any other MCP-aware client.
Install
npm install -g @mailsink/mcpOr run via npx without installing:
npx @mailsink/mcpGet an API key
or .env.
- Sign in at with GitHub.
- Copy the key from the one-time reveal. Store it in your password manager
- Export it so the MCP server can read it:
export MAILSINK_API_KEY="msk_..."Free tier is 50 inboxes/month and includes MCP. Pro ($15/mo) and Team ($49/mo) lift the inbox cap, raise email size limits, extend TTL, and bump request rates. See pricing.
Configure your client
Claude Code
claude mcp add mailsink -- npx -y @mailsink/mcpClaude Desktop / Cursor / Windsurf
Add to the mcpServers section of the client's config file:
{
"mcpServers": {
"mailsink": {
"command": "npx",
"args": ["-y", "@mailsink/mcp"],
"env": {
"MAILSINK_API_KEY": "msk_..."
}
}
}
}Restart the client. You should see the mailsink server listed with its eight tools.
Tools
Example agent flow
> Sign me up for Figma, capture the verification code, confirm, and
> tell me the plan once you're in.
[agent invokes]
create_inbox() → agent@codenotify.net
[agent fills the Figma signup form with that address]
wait_for_email(inbox_id) → blocks 30s…
→ returns email + OTP
[agent types the OTP into the Figma form]
delete_inbox(inbox_id) → cleanupNo webhook plumbing. No IMAP credentials. No parsing MIME.
Environment variables
override for self-hosted or dev API.
- MAILSINKAPIKEY (required) — your account's API key.
- MAILSINKAPIURL (optional, default https://api.mailsink.dev) —
Source
License
MIT — see LICENSE.
Nothing above is checked by us. What we check is on the safety report.
Mailsink: common questions
- Is Mailsink MCP server safe?
- Mostly: it is graded B (78/100). Read the Mailsink safety report
- How do I install Mailsink?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Mailsink need an API key?
- Yes. The registry entry asks for
MAILSINK_API_KEY. - Is Mailsink maintained?
- The last commit was 75 days ago (2026-08-21). The latest release is v0.1.5.
- What can I use instead of Mailsink?
- Servers from other publishers that do the same job: send0 MCP server, smails MCP server and EmptyInbox MCP server.
- How does Mailsink compare with other Email MCP servers?
- safety score 78/100 (higher than 62% of 916 Email servers); tools 8 (the typical Email server has 7); tools that change things 38% (typical: 25%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Mailsink
Same job from other publishers: the closest match first, then the best rated.
- send0Email inboxes for AI agents: create an address, wait for codes and links, send and reply in threads.not reviewedGrowingA
- smailsFree disposable email for AI agents: a throwaway inbox to read verification codes over MCP.not reviewedGrowingB
- EmptyInboxZero-config disposable email inboxes for AI agents: create, read mail, await verify codes.not reviewedGrowingB
- e2a — email for AI agentsAuthenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.not reviewedEstablishedA
- AgenticmailReal email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.not reviewedEstablishedB