Proxy Mail QA

qa.proxymailPublished by proxymail.qaOfficial publisherv1.8.0Updated Oct 25, 2026

Test inboxes for your app's sign-up and login emails: get the code or link, or why none came.

VerifiedStreamable HTTPWeb executableDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

A remote MCP server that gives an assistant test inboxes for your app's sign-up and login emails, so it can fetch the code or link, or see why none arrived.

What you can do
Work with test inboxes for your app's sign-up and login emails: retrieve the verification code or link from a message, or find out why no email came. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when testing sign-up, login or other email-driven flows and you want an assistant to read the delivered message and pull out the code or link instead of checking a mailbox by hand.
Requirements
A remote endpoint at api.proxymail.qa over streamable HTTP. Authentication is required: OAuth sign-in, or an Authorization header carrying a bearer API key taken from Project settings → API keys in the provider's app.
Before you install
The server handles authentication email contents, including verification codes and links, so treat that data as sensitive. The Authorization header carries a secret API key; keep it out of logs and shared configuration. Emails and codes are sent to the remote provider.

Installation

In SourceWeft

  1. Open Proxy Mail QA 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/qa.proxymail%2Fproxymail-qa/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": {
    "proxy-mail-qa": {
      "type": "http",
      "url": "https://api.proxymail.qa/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

6
  1. v1.8.0LatestOct 25, 2026
  2. v1.7.0Oct 22, 2026
  3. v1.6.0Oct 21, 2026
  4. v1.5.0Oct 18, 2026
  5. v1.4.0Oct 18, 2026
  6. v1.0.0Oct 12, 2026

Score

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