myagentinbox

com.myagentinboxPublished by myagentinbox.comOfficial publisherv0.1.0Updated Oct 24, 2026

Disposable email inboxes for AI agents. Auto-deletes after 24 hours.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Gives an assistant a disposable email inbox that receives messages and expires automatically after 24 hours.

What you can do
This remote MCP server provides disposable email inboxes intended for AI agents. According to the registry description, inboxes are temporary and auto-delete after 24 hours. No tool list is published, so the exact operations (for example creating an inbox, reading messages, or waiting for a message) are not documented in the supplied material.
When to use it
Consider it when an assistant needs a throwaway address to receive a confirmation link, verification code, or test message without using a personal or shared mailbox. It is less suitable when mail must be kept longer than 24 hours or when a permanent, auditable mailbox is required.
Requirements
A remote MCP endpoint at over streamable HTTP. No packages, environment variables, or headers are declared, and the manifest declares no authentication. Network access to the provider is required.
Before you install
The manifest declares no authentication, so anyone who can reach the endpoint may be able to create or read inboxes; treat anything received as non-private. Inbox contents are deleted after 24 hours, so do not rely on them for records. Messages pass through the provider's servers, and no tool list is published, so verify what the server can do before use.

Installation

In SourceWeft

  1. Open myagentinbox in the dashboard and add it to a workspace.
  2. 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.myagentinbox%2Fmyagentinbox/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": {
    "myagentinbox": {
      "type": "http",
      "url": "https://myagentinbox.com/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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