fixture.email — Email Testing for Agents

email.fixturePublished by fixture.emailOfficial publisherv1.0.0Updated Oct 24, 2026

Disposable test mailboxes on a real domain: send, receive and assert on real email.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant create disposable test mailboxes on a real domain and send, receive and assert on real email.

What you can do
This remote server provides disposable test mailboxes on a real domain. According to the registry description, it lets an assistant send email, receive email and assert on real email, which supports automated email testing. No individual tools are listed in the manifest.
When to use it
Useful when an assistant needs to exercise email flows end to end, such as sign-up confirmations or transactional messages, against real mailboxes rather than mocks.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is required via OAuth, and an org-scoped API key is supplied in the X-API-Key header. Network access to the remote endpoint is required.
Before you install
The X-API-Key header carries an org-scoped secret; keep it out of logs and shared configuration. The server can send real email from a real domain and read received messages, so test content and recipients should be chosen deliberately.

Installation

In SourceWeft

  1. Open fixture.email — Email Testing for Agents 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/email.fixture%2Femail-testing/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": {
    "fixture-email-email-testing-for-agents": {
      "type": "http",
      "url": "https://mcp.fixture.email/mcp"
    }
  }
}

README

This repository has no README.

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.0LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Fixture integrations