Test Mailbox

io.github.therealMrFunGuyPublished by GitHub account therealMrFunGuyv1.0.0Updated Oct 25, 2026

Disposable email inboxes for testing — create addresses, wait for messages, extract links.

The publisher's own server: mailbox.bot

VerifiedSSEWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that gives an assistant disposable email inboxes for testing: create addresses, wait for incoming messages, and extract links.

What you can do
Create disposable email addresses for test scenarios, each with its own inbox and API key. Wait for messages to arrive at an address and read their contents. Extract links from received messages, for example to complete sign-up or verification flows.
When to use it
Useful when testing sign-up, email verification, password reset, or other flows that require a working inbox, and you want an assistant to create throwaway addresses and pull verification links automatically.
Requirements
A remote SSE endpoint; no local package or runtime is needed. An API key supplied in the X-API-Key header, obtained from the provider's auth dashboard. Network access to the provider's endpoint.
Before you install
The server asks for an API key in the X-API-Key header; keep it private. Inboxes are disposable and hosted by a third party, so any messages sent to those addresses pass through that provider and should not contain sensitive data. The provider's dashboard link is where the key is issued.

Installation

In SourceWeft

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

Web executable via SSE. 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.github.therealMrFunGuy%2Ftest-mailbox/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": {
    "test-mailbox": {
      "type": "sse",
      "url": "https://mail.rjctdlabs.xyz/sse"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 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 listedRequired15 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.

Other Mailbox integrations