Mailfornet

com.mailfornetPublished by mailfornet.comOfficial publisherv1.0.0Updated Oct 24, 2026

Disposable email inboxes for AI agents: create an address, wait for the OTP or verify link.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that gives an assistant disposable email inboxes so it can create an address and wait for an OTP or verification link.

What you can do
Create disposable email addresses for an assistant to use during sign-up or verification flows. Wait for incoming mail such as one-time passcodes or verification links. Retrieve the message contents so the assistant can continue the flow. No tool list is published, so exact operations are not documented.
When to use it
Useful when an assistant needs to complete a sign-up, login or verification step that requires an email address and a code or link, and you do not want to expose a real mailbox.
Requirements
A remote endpoint reached over streamable HTTP. A Mailfornet API key is required, sent in the Authorization header; a free tier is offered at sign-up. Network access is needed.
Before you install
The API key in the Authorization header is a secret and should be kept out of logs and shared transcripts. Inboxes are disposable and may be readable by others or expire, so do not route sensitive accounts or personal mail through them. The service sees the messages delivered to those addresses.

Installation

In SourceWeft

  1. Open Mailfornet 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/com.mailfornet%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.

{
  "mcpServers": {
    "mailfornet": {
      "type": "http",
      "url": "https://api.mailfornet.com/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.0LatestSep 25, 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.