fabricatedemail

com.fabricatedemailv1.0.0Updated Oct 7, 2026

Disposable email addresses for tests and agents: register, wait for mail, extract codes and links.

VerifiedStreamable HTTPWeb executableDeveloper Tools Communication & Collaboration

Overview

AI-generated overview

Lets an assistant create disposable email addresses, wait for incoming mail, and pull one-time codes or links out of messages.

What it does: A remote MCP server for throwaway inboxes used by tests and agents. Tools include create_address to register a disposable address, wait_for_message to long-poll for arriving mail, extract to pull one-time codes and links from a message, get_message to read a stored message, list_addresses to see the live addresses held by the key, and delete_address to remove an address and its stored mail. It mirrors the provider's HTTP API, so caps, retention, and rate limits are the same as a CI job.
When to use it: Useful when an assistant or automated test needs a real inbox to receive a signup confirmation, verification code, or magic link without setting up SMTP or inbound networking. It fits end-to-end test flows and agent workflows that must complete an email verification step.
Requirements: A remote streamable HTTP endpoint; no local package or runtime. An API key created in the provider's dashboard, sent as an Authorization bearer token header. A free account is available and needs no card. Network access to the provider's API is required.

Before you install

The Authorization header carries a secret API key; use a key minted for the agent so it can be revoked separately. Revoking a key deletes the addresses it created and their mail, and delete_address removes an address and its stored mail. Mail content is handled by the third-party service, and the same key, caps, retention, and rate limits apply as to the HTTP API.

Installation

In SourceWeft

Open fabricatedemail in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mcp": {
      "type": "http",
      "url": "https://api.fabricatedemail.com/mcp"
    }
  }
}

README

fabricatedemail MCP server

Disposable email addresses for automated tests and coding agents. An agent that needs an email address and the message that lands in it connects to the server, registers an address, has the system under test send mail to it, waits for the message, and pulls the one-time code or link out of it — without regular expressions, SMTP, or any inbound network access on its side.

The server is remote, at https://api.fabricatedemail.com/mcp, over streamable HTTP, and takes an API key as a bearer token. Keys are created in the dashboard; a Free account needs no card. The full guide is at https://fabricatedemail.com/docs/mcp.

Connecting a client

Most MCP clients take an HTTP endpoint and a header:

json

{  "mcpServers": {    "fabricatedemail": {      "type": "http",      "url": "https://api.fabricatedemail.com/mcp",      "headers": { "Authorization": "Bearer <api-key>" }    }  }}

{  "mcpServers": {    "fabricatedemail": {      "type": "http",      "url": "https://api.fabricatedemail.com/mcp",      "headers": { "Authorization": "Bearer <api-key>" }    }  }}

Use a key minted for the agent rather than the one your CI uses, so you can revoke it on its own. Revoking a key deletes the addresses it created and their mail.

The tools

Tool	What it does
`create_address`	register a disposable address
`wait_for_message`	wait for mail and return what is there
`extract`	one-time codes and links from a message
`get_message`	read one stored message
`list_addresses`	the live addresses this key holds
`delete_address`	delete an address and its stored mail

The tools are the HTTP API: the same caps, the same retention and the same 30-second long poll, on the same key and the same rate limit as a CI job. Nothing an agent can do here falls outside the HTTP contract.

What this repository is

The server's code lives in the API, not here. This repository holds the server's entry in the MCP registry: server.json, the manifest the registry reads; logo.png, the picture shown beside it; and the workflow that publishes a tagged version (.github/workflows/publish.yml).

Source: README.md at commit 79ec21d

Tools

Tool metadata has not been indexed yet.

Version history

v1.0.0LatestOct 7, 2026