BlinkInbox

club.blinkinboxPublished by blinkinbox.clubOfficial publisherv1.0.0Updated Oct 24, 2026

Disposable email inboxes for AI agents: create an address, wait for mail, read OTP codes and links.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Gives an AI assistant disposable email inboxes: create an address, wait for incoming mail, and read OTP codes and links.

What you can do
BlinkInbox is a remote MCP server that provides disposable email inboxes for AI agents. According to its description, an assistant can create an email address, wait for mail to arrive, and read one-time passcodes and links from received messages. No individual tools are listed in the manifest, so the exact tool names and parameters are not documented here.
When to use it
Useful when an assistant needs a throwaway address to receive a verification code or confirmation link during a sign-up or test flow, without using a real personal mailbox. It suits automated workflows that must wait for and extract codes or links from incoming email.
Requirements
A remote MCP server reached over streamable HTTP at the provider's endpoint. Authentication is OAuth and is required; no environment variables or headers are declared. Network access to the provider is needed.
Before you install
The server handles incoming email, including one-time passcodes and links, which are sensitive; anyone with access to the inbox may be able to read them. Disposable inboxes may be blocked or rejected by some services, and mail content passes through the provider. Review the provider's terms and data handling before relying on it for account verification.

Installation

In SourceWeft

  1. Open BlinkInbox 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/club.blinkinbox%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": {
    "blinkinbox": {
      "type": "http",
      "url": "https://api.blinkinbox.club/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. v1.0.0LatestOct 13, 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.