npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@legendtrading/testmail-mcp

v1.0.2

Published

MCP server for the Legend testmail temporary email + TOTP service

Readme

@legendtrading/testmail-mcp

MCP (Model Context Protocol) server for the Legend testmail service (mail.legendcoding.com) — gives any MCP-capable agent (Claude Desktop, Cursor, Cline, …) native tools for temporary email and 2FA/TOTP: create a mailbox, wait for a verification email, read it, send, produce login 2FA codes, and clean up.

It shares the same HTTP client and config as the CLI via @moemail/core, so it talks to the exact same API (authenticated with an X-API-Key).

Tools

| Tool | Description | |------|-------------| | create_email | Create a temporary mailbox (expiry: 1h / 24h / 3d / permanent) | | list_emails | List mailboxes owned by the API key | | list_messages | List messages in a mailbox | | read_message | Read full text/HTML of a message | | wait_for_email | Poll for a new message (bounded, max 90s; returns status: "timeout" to retry) | | send_email | Send from a temporary address (needs send permission) | | delete_email | Delete a mailbox | | delete_message | Delete a single message | | add_totp | Attach a 2FA secret (otpauth:// URI or raw base32) to a mailbox; returns the new totpId and current code | | list_totp | List the 2FA (TOTP) entries on a mailbox, each with its current code | | get_totp_code | Get the current 6-digit TOTP code for an entry (defaults to the mailbox's only entry) | | delete_totp | Remove a 2FA (TOTP) entry from a mailbox |

Configuration

The server reads credentials from environment variables:

  • MOEMAIL_API_KEY (required) — your testmail API key (mk_…)
  • MOEMAIL_API_URL (optional) — defaults to https://mail.legendcoding.com

Usage

Add to your MCP client config (e.g. Claude Desktop claude_desktop_config.json):

{
  "mcpServers": {
    "legend-testmail": {
      "command": "npx",
      "args": ["-y", "--package=@legendtrading/testmail-mcp", "testmail-mcp"],
      "env": {
        "MOEMAIL_API_KEY": "mk_xxx",
        "MOEMAIL_API_URL": "https://mail.legendcoding.com"
      }
    }
  }
}

⚠️ Use the explicit --package=<pkg> testmail-mcp form, not npx -y @legendtrading/testmail-mcp. npm shipped with Node 24+ mis-infers the command name from a scoped package and fails with testmail-mcp: command not found; separating the package from the binary name avoids this.

Notes

  • API keys authenticate against /api/emails*, /api/config*, and the TOTP endpoints — the same surface the CLI uses.
  • Authentication, permission, and rate-limit failures from the server are surfaced as descriptive tool errors rather than generic failures.