Temp Mail

io.temp-mailPublished by temp-mail.ioOfficial publisherv1.0.1Updated Oct 24, 2026

Disposable email inboxes for AI agents — read messages and verification codes.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that gives an AI assistant disposable email inboxes to read messages and verification codes.

What you can do
Create and use disposable email inboxes for an assistant session, as described in the registry entry. Read incoming messages delivered to those inboxes. Retrieve verification codes from received mail so an assistant can complete sign-up or login flows. No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when an assistant needs a throwaway address to receive a confirmation email or verification code without exposing a personal or work inbox. Suited to short-lived sign-ups and automated flows where the mailbox is not meant to be kept.
Requirements
A remote endpoint at api.temp-mail.io over streamable HTTP. Authentication is required and uses OAuth, so the user must complete an OAuth authorization flow. No environment variables, headers or packages are declared.
Before you install
The service receives and holds mail sent to the disposable addresses, so anything delivered there passes through a third party. Verification codes and sign-up links in that mail are sensitive; avoid using it for accounts that matter. OAuth grants access to the service under the user's account.

Installation

In SourceWeft

  1. Open Temp Mail in the dashboard and add it to a workspace.
  2. Connect the required 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/io.temp-mail%2Ftemp-mail/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "temp-mail": {
      "type": "http",
      "url": "https://api.temp-mail.io/v1/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.