MailFixture

com.mailfixturePublished by mailfixture.comOfficial publisherv0.1.0Updated Oct 24, 2026

Test-inbox API for email and SMS: create inboxes, long-poll messages, extract OTPs and links.

VerifiedStreamable HTTPWeb executableDeveloper ToolsCommunication & Collaboration

Overview

AI-generated overview

A remote test-inbox API that lets an assistant create email and SMS inboxes, wait for incoming messages, and pull out OTPs and links.

What you can do
Create test inboxes for email and SMS reception, then long-poll them for incoming messages. Extract one-time passcodes and links from received messages. Useful for automating sign-up and verification flows during testing.
When to use it
Use it when an assistant needs to receive verification emails or SMS in an automated test or sign-up flow and read the code or link without a human checking a mailbox.
Requirements
A remote endpoint at mailfixture.com over streamable HTTP. A MailFixture API key is required, sent as a bearer token in the Authorization header.
Before you install
The API key is a secret sent in the Authorization header; keep it out of logs and shared transcripts. Inboxes and messages are test data held by a third party, so do not route real personal or production email and SMS through it.

Installation

In SourceWeft

  1. Open MailFixture 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.mailfixture%2Fmailfixture/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": {
    "mailfixture": {
      "type": "http",
      "url": "https://mailfixture.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. v0.1.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 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.