Proxy Mail QA
Proxy Mail QA v1.8.0
Test inboxes for app sign-ups
From the developer
Declared capabilities
- Read
- Write
Declared limitations
- Sending email isn't supported: Proxy Mail QA addresses are receive-only, so no tool should run and the reply should say so.
- Personal inboxes are out of scope: Proxy Mail QA only reads its own test addresses, so no tool should run.
- Passwords saved earlier can't be read through this connection (only a new address's password is shown, once, when it's created), so it should explain that and point to the Proxy Mail QA app.
- Real accounts are out of scope: set_password only records the password of a Proxy Mail QA test address, so no tool should run and the reply should say it can't change passwords on other services.
Not specified in the available declarations: pricing & account requirements.
Onboarding example
Give me a test email for my sign-up form and tell me the code when it arrives.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 6, 2026. Package observed Nov 6, 2026.
Description
From the marketplace listing
Proxy Mail QA gives ChatGPT and Codex disposable email addresses for testing the emails your app sends. Ask things like: - "Give me a test email for my staging sign-up and tell me the code when it arrives." - "Why isn't my app's verification email arriving?" - "Check the password-reset email my app sent to my test address." - "Sign up on localhost:3000 with a new test account and confirm the email." (Codex, or an agent with a browser) It creates an address with a fictional name, username and, if the form needs one, a strong password. You sign up with it, or the agent does when it can use a browser, and you get the verification code or link as soon as it arrives. It works the same for login codes, magic sign-in links, password resets and invites, and it can check the email itself: SPF, DKIM and DMARC, links that point at localhost, the stated expiry and how it fits on a phone. When nothing arrives, it shows what reached the address, anything refused, and the likely cause. It can also fill a whole sign-up form's values (a username with rules, a date of birth, a country), suggest awkward names and passwords to test a form's validation, and look up how something works in Proxy Mail QA's docs. Results contain only the code or link, the service that sent it and when it expires, never the email's text, so an email can't pass instructions to your agent. Proxy Mail QA never opens links, so single-use links still work. Addresses last up to 30 days and only you can read their mail. Addresses are receive-only: nothing is ever sent from them. When you connect, you sign in to Proxy Mail QA (or create an account and your first project on the way) and choose one project; the agent works only in that project and can't read passwords saved earlier. Disconnect it any time in Project settings → API keys.
Language: English · Automatically detected from descriptions.
Matches for “write app code”
Exact text from the indicated source. A mention alone does not establish support for your task.
Publisher full description
Proxy Mail QA gives ChatGPT and Codex disposable email addresses for testing the emails your app sends. Ask things like: - "Give me a test email for my staging sign-up and tell me the code when it arrives." - "Why isn't my app's verification email arriving?" - "Check the password-reset email my app sent to my test address." - "Sign up on localhost:3000 with a new test account and confirm the email." (Codex, or an agent with a browser) It creates an address with a fictional name, username and, if the form needs one, a strong password. You sign up with it, or the agent does when it can use a browser, and you get the verification code or link as soon as it arrives. It works the same for login codes, magic sign-in links, password resets and invites, and it can check the email itself: SPF, DKIM and DMARC, links that point at localhost, the stated expiry and how it fits on a phone. When nothing arrives, it shows what reached the address, anything refused, and the likely cause. It can also fill a whole sign-up form's values (a username with rules, a date of birth, a country), suggest awkward names and passwords to test a form's validation, and look up how something works in Proxy Mail QA's docs. Results contain only the code or link, the service that sent it and when it expires, never the email's text, so an email can't pass instructions to your agent. Proxy Mail QA never opens links, so single-use links still work. Addresses last up to 30 days and only you can read their mail. Addresses are receive-only: nothing is ever sent from them. When you connect, you sign in to Proxy Mail QA (or create an account and your first project on the way) and choose one project; the agent works only in that project and can't read passwords saved earlier. Disconnect it any time in Project settings → API keys.
Publisher subtitle
Test inboxes for app sign-ups
Publisher capabilities · listing
Read Write
Publisher description
Disposable test inboxes for testing sign-up, login-code, magic-link and password-reset emails. Create an address, sign up with it, and get the code or link back without the rest of the email.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Oct 28, 2026. Last seen Nov 6, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Build, test, and deploy any application
Shared terms: test, testing
-
Connect ChatGPT to QA Wolf to inspect authorized workspaces, explore a staging app in a cloud browser, request test implementation from Q...
Shared terms: test, browser, staging, code
-
Email inbox for AI agents. Give the agent its own inbox: read mail that wants a reply, reply in-thread, send new mail, manage custom doma...
Shared terms: inboxe, address, mail, email
-
Cooper Email gives ChatGPT its own real email address. Connect, sign in on Cooper's OAuth screen (create an inbox or link an existing key...
Shared terms: inboxe, address, mail, username
-
Check your SecureSMTP account, manage sending domains, see delivery stats and send email.
Shared terms: addresse, confirm, form, mail
Keywords
Files & skills
File archives
Skill instructions
proxymail-qa15.3 KB
---
name: proxymail-qa
description: Test sign-up, email verification, login-code (OTP), magic-link, password-reset and invite flows with disposable Proxy Mail QA inboxes. Use when a task needs a fresh email address for an app under test and the code or link from the email it receives.
---
# Testing email flows with Proxy Mail QA
Proxy Mail QA gives you disposable email addresses and hands back the verification code or link from each email that arrives, without the rest of the email. It supplies the inbox and the details for a sign-up form; it doesn't create accounts in the app or fill in its forms. You sign up in the app with your own browser or app tools.
## Setup
This plugin adds the Proxy Mail QA MCP server (tools named `create_address`, `wait_for_code`, `wait_for_link`). It signs in through the browser: if the tools aren't available yet, ask the person you're working for to connect Proxy Mail QA, sign in and choose a project. There's no key to set up.
## Test a sign-up
1. Check the project with `get_project`. It gives the project's default mail domain and the others available, the prefix addresses start with, and how long they last. Don't assume a domain: the ones in examples here aren't necessarily this project's.
2. Create an address with `create_address`, with a password if the sign-up form asks for one: `{"label": "Sign-up test", "password": true}`. It also returns a fictional first name, last name and username. The password comes back once, in this result, and is saved on the address so the person can sign in as the test account later. If the form asks for a date of birth, add `"age": "adult"` (or `over21`, `under18`, `under15`, `under13`, `any`, `turns18tomorrow`, `turned18today`): the persona then has `date_of_birth`, YYYY-MM-DD. Write it in the order the form asks for. If it asks where they live, or the test is about a region, add `"country": "GB"` (any ISO 3166-1 alpha-2 code). Add where the account is used: `"site"` (the app's host or the page URL, such as `staging.example.com`) and `"environment"` (such as `staging`, `qa` or `local`). The person sees both on the account in the app, and `list_addresses` finds accounts by them.
3. Fill in the app's form with the address, persona and password, and submit it. For a form with more than an email field (a username with rules, a date of birth, a country drop-down), use `form_values` instead of `create_address`: send what the page says about each field (`id`, `type`, `name`, `label`, `placeholder`, `autocomplete`, `pattern`, `min_length`, `max_length`, and a drop-down's `options`), and it returns the value for each field from a new address made for the form, its password included. You still fill in the form and submit it.
4. Wait for what the email contains:
- A code: `wait_for_code` with `{"address": "…"}`
- A link: `wait_for_link` with `{"address": "…"}`, and `kind` `reset` or `magic_signin` for those emails
Each waits up to 30 seconds and also returns a match from the last 15 minutes.
5. Enter the code, or open the link if the task calls for it. Many forms split a code into one box per digit. Click the first box and type the whole code: most move to the next box on each digit, and many spread a pasted code across them. If a box keeps only one character and focus doesn't move, fill each box with its own digit, in order. Before submitting, check (with a screenshot, or by reading the boxes) that every digit is in place: a partial code counts as a wrong attempt, and many apps lock the account after a few.
6. Record what the account is for with `update_address` and `notes`.
If the app changes the test account's details, keep the saved ones in step so the person can still sign in as it: save a new password with `set_password` (`{"address": "…", "password": "…"}`, or leave `password` out to generate one, returned once), and a new name or username with `update_address` and `first_name`, `last_name` or `username`.
## Check it worked
- The app shows the accounPreview of the first 4,000 characters. Read full instructions →
Release notes
Since 1.0.1: checks on the emails a test address receives (check_email: SPF, DKIM, DMARC, links to localhost or plain http, where links go, a stated expiry, size and how it fits a phone; count_emails to catch duplicates; expect_no_email to check an action sends nothing), all verdicts, never the email. Runs (start_run, add_run_note, finish_run) record what each tool saw and end in a Markdown report. An account pool (check_out_account, extend_checkout, return_account) lends a test account in a known state. form_values fills a whole sign-up form's values, get_name_variants and get_password_variants suggest awkward names and passwords to test a form's validation, and search_docs looks things up in the docs. Accounts can record the site and environment they're used on, mark_dev_host lets links to a local dev server pass the checks, and waits can skip codes already used. Ready-made prompts for testing sign-up, password reset and code sign-in, auditing an app's account emails and preparing a test account. Checks on an app's marketing emails (unsubscribe links, codes in them, consent) work for people who switch them on in Labs.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package license
- MIT
- Package author
- Proxy Mail QA
- Keywords
- See keywords
- Review scenarios
- 17 positive · 4 negativeScenario counts, not test results.
Declared capabilities
- Read
- Write
Package observed Nov 6, 2026.
Technical details
- First seen
- Oct 28, 2026 · 12:00 UTC
- Last seen
- Nov 6, 2026 · 06:00 UTC
- Collection status
- Collected
plugin_asdk_app_6acde757c5748191af402b25494ad875
Download plugin data (JSON)