mcpbeat Sign in

send0 MCP Server

by send0-dev Your server? Claim it
answering

send0 is answering right now. Last checked 11 min ago. 412 installs a week from npm. Last commit 13 Oct 2026.

Email inboxes for AI agents: create an address, wait for codes and links, send and reply in threads.

Installs per day peak 365 · avg 13
a month agotoday
Uptime history 68 hours of history
68 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
440 ms
Response time
average over 24h
412
Installs / week
npm and PyPI

What the code does

We read the source, 1 d ago · rules ccca72095570

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Builds a file path from a variable apps/www/brand/build.mjs:18
const mod = (p) => path.join(root, "node_modules", p);

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add send0 --transport http https://api.send0.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "send0": {
      "url": "https://api.send0.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.send0]
url = "https://api.send0.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "send0": {
      "url": "https://api.send0.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "send0": {
      "url": "https://api.send0.dev/mcp"
    }
  }
}

This one needs environment variables set before it will start: SEND0_API_KEY (send0 API key (s0_live_…), from https://app.send0.dev), SEND0_INBOX_ID (Default inbox (ibx_…) for tools that take an inbox_id), SEND0_BASE_URL (API base URL, for a self-hosted send0). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://api.send0.dev/mcp streamable-http needs key 292 ms 11 min ago

Alternatives to send0

same job, measured the same way
BlinkInbox
by blinkinbox

Disposable email inboxes for AI agents: create an address, wait for mail, read OTP codes and links.

answering
Agentboxd
by agentboxd

Real email inboxes for AI agents: create addresses, send, wait for mail and verification codes.

answering
Poofbox Mail
by poofboxmail

Disposable inboxes for AI agents: create an address, wait for the email, get the code or link.

answering
MailFlat
by mailflat

Real email inboxes for AI agents: open an address, read the one-time code, send mail.

380 installs/wk local only
AI Mail MCP
by aimailmcp

Real email for AI agents: domains, mailboxes, a unified inbox, wait-for-code, send and reply.

answering
Proxy Mail QA
by proxymail

Disposable test inboxes for agents: create an address, then wait for its code or link.

answering
Machine Inbox
by machineinbox

Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.

11 tools answering
Mail for Bots
by mailforbots

Email inboxes for AI agents: send, reply, read verification codes, human-approved drafts.

answering

send0 — questions

Answers built from our own checks of this server.

Why is there no tool list for send0?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is send0 working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 440 ms. The bar chart above shows every period we have measured.
How do I connect send0?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.
Does send0 need an API key?
Yes. Every time we knock, send0 answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is send0?
It answers our handshake in 440 ms on average, which is faster than 27% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use send0?
The npm package @send0/mcp was installed 412 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is send0 open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.