Fake Email

pro.fake-emailPublished by fake-email.proOfficial publisherv1.0.0Updated Nov 22, 2026

Disposable email inboxes for AI agents: wait for an email and get its OTP code and confirm link

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server giving AI agents disposable email inboxes so they can wait for a message and pull out its OTP code or confirmation link.

What you can do
  • Receive mail in disposable inboxes created for an agent
  • Wait for an incoming email to arrive
  • Extract one-time passcodes (OTP) from received messages
  • Retrieve confirmation or verification links from emails
  • No tool list is published, so exact operations are not documented
When to use it
Useful when an assistant must complete sign-up or login flows that send a verification code or confirmation link by email and you do not want to expose a real mailbox.
Requirements
A remote endpoint at api.fake-email.pro over streamable HTTP. A Fake Email API key sent as a Bearer token in the Authorization header; the key is free with an account, no card required.
Before you install
The Authorization header carries a secret API key, so keep it out of logs and shared configs. Inboxes and messages are handled by a third-party service, so do not route sensitive or personal email through it. Verification codes and links it retrieves can grant access to accounts.

Installation

In SourceWeft

  1. Open Fake Email in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/pro.fake-email%2Ffake-email/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "fake-email": {
      "type": "http",
      "url": "https://api.fake-email.pro/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.