DropMail

me.dropmailPublished by dropmail.meOfficial publisherv0.2.0Updated Nov 12, 2026

Disposable temporary email: create inboxes, wait for and read incoming mail. No account needed.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

DropMail gives an assistant disposable temporary email inboxes it can create, then wait for and read incoming messages in.

What you can do
  • Create a disposable temporary inbox
  • Wait for and read incoming mail delivered to that inbox
  • No tool list is published, so the exact operations are not documented beyond creating inboxes and reading mail
When to use it
Useful when a workflow needs a throwaway address to receive a confirmation or sign-up message without exposing a real mailbox, for example during testing or one-off sign-ups.
Requirements
A remote MCP endpoint at dropmail.me over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared, and no account is said to be needed.
Before you install
The service is a third-party mail host: anything sent to a temporary inbox passes through it, so do not use it for sensitive or confidential messages. Mailboxes are disposable and messages may be lost or expire. OAuth grants the server access under your authorization.

Installation

In SourceWeft

  1. Open DropMail 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/me.dropmail%2Fmcp/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": {
    "dropmail": {
      "type": "http",
      "url": "https://dropmail.me/api/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. v0.2.0LatestNov 12, 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.