Skip to content
Receivemail logo

Receivemail MCP server

Which MCP servers are Receivemail's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-02

← Back to Receivemail

Whose server it is
  • Registry namedev.receivemail/receivemailverified in the MCP registry

The registry name sits under receivemail.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-02
  • Stateanswerschecked 2026-11-02
  • Tools3
  • Server calls itselfreceivemail
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-11-02 the server answered initialize and tools/list without a sign-in. First answer in 52 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Create throwaway email addresses for test runs; Wait for verification emails inside automated test suites; Read one-time codes from signup emails in tests.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Create throwaway email addresses for test runs", the likely first call is create_mailbox.
  • For "Wait for verification emails inside automated test suites", the likely first call is create_mailbox.
  • For "Read one-time codes from signup emails in tests", the likely first call is create_mailbox.
  • create_mailbox change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-11-02
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer150 ms
  • Space in an agent's context≈ 424 tokensthe definitions of all its tools (3), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · Create throwaway email addresses for test runs
  • can do · Wait for verification emails inside automated test suites
  • can do · Read one-time codes from signup emails in tests

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: create_mailbox

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-11-02
  • create_mailbox

    Create a disposable receivemail.dev email address that receives real mail. Returns address, expiresAt and secret; keep the secret to read the mailbox. Free without a key (up to 60 minutes); with a paid key on the MCP connection, up to…

  • wait_for_email

    Wait up to 25 seconds for an email to a mailbox made with create_mailbox. Returns {timed_out:false, message:{from_address, subject, body_text, received_at}} or {timed_out:true}; call again on timeout. Pass `since` (ISO 8601) to ignore…

  • list_messages

    List the last 50 emails received by a mailbox made with create_mailbox, newest first.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "receivemail": {
      "type": "http",
      "url": "https://receivemail.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http receivemail https://receivemail.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://receivemail.dev/mcp as a custom connector in the settings.

OpenAPI spec

4 paths, read 2026-11-02. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.