Proxy Mail QA llms.txt changelog

https://proxymail.qa/llms.txt

− - Works with emails from Supabase Auth, Firebase Authentication, Clerk, Auth0 and most apps that send transactional email, as long as the app's email provider can send to any address. Providers in sandbox or test mode (Amazon SES before production access, Resend without a verified domain, Mailgun sandbox domains, Postmark before approval, Supabase's built-in email) only send to verified addresses, so no test inbox can receive their mail.− - [MCP server and plugins](https://proxymail.qa/features/mcp): connecting each client, the tools, browser sign-in and security, the Claude Code plugin, the Cursor Directory listing (https://cursor.directory/plugins/proxymail-qa), the agent skill and the MCP Registry listing−   - [MCP server for each client (Claude Code, Cursor, GitHub Copilot, Antigravity, Codex, Windsurf, Zed, Kiro, OpenCode, Kilo Code, Roo Code, Augment Code, Trae, Mistral Vibe, Qwen Code, Kimi CLI, JetBrains IDEs, Claude and ChatGPT) and its tools](https://proxymail.qa/docs/mcp)−   - [Labs](https://proxymail.qa/docs/labs): features a person switches on in Account settings → Labs before they're available to everyone. Now: Marketing and offer emails (the Offers and Marketing areas, record_coupon_result, check_offers, mark_unsubscribed, mark_resubscribed, check_unsubscribe, record_consent, check_sequence and the coupon and marketing checks), and Spam score and attachment checks (spam_risk, harmful_attachment). API keys and agents follow their creator's switches; while off, − - [MCP server](https://api.proxymail.qa/mcp) (Streamable HTTP; signs in by browser, or an API key as bearer). Tools: get_project, create_address (an address with a persona, a date of birth for an age and a country if asked, a password for the sign-up form if asked, and the site and environment it's used on), form_values (what to type or pick in each field of a sign-up form, from what the page says about each), wait_for_code (kind: coupon for a coupon or promo code, with its discount and valid-un− - Sign-in: an API key created by a signed-in person in Project settings → API keys, or OAuth (claude.ai, ChatGPT and other MCP clients sign in by browser and the person chooses a project). Available on the Free plan (60 requests a minute per key).− - [Qoder](https://proxymail.qa/built-with/qoder)− ## Guides: auth providers (the emails Supabase, Clerk, Auth0, Firebase, Auth.js and Better Auth send, and their sending limits)+ - Works with emails from Supabase Auth, Firebase Authentication, Clerk, Auth0, Amazon Cognito and most apps that send transactional email, as long as the app's email provider can send to any address. Providers in sandbox or test mode (Amazon SES before production access, Resend without a verified domain, Mailgun sandbox domains, Postmark before approval, Supabase's built-in email) only send to verified addresses, so no test inbox can receive their mail.+ - [MCP server and plugins](https://proxymail.qa/features/mcp): connecting each client, the tools, browser sign-in and security, the Claude Code plugin, the Cursor Directory listing (https://cursor.directory/plugins/proxymail-qa), the ChatGPT plugin directory listing (https://chatgpt.com/plugins/plugin_asdk_app_6acde757c5748191af402b25494ad875), the Qoder Marketplace connector (https://qoder.com/en/marketplace/connector?id=proxymail-qa) and plugin (https://qoder.com/en/marketplace/plugin?id=3b572+   - [MCP server for each client (Claude Code, Cursor, GitHub Copilot, Antigravity, Codex, Windsurf, Zed, Kiro, Amazon Q Developer, OpenCode, Kilo Code, Roo Code, Augment Code, Trae, Mistral Vibe, Qwen Code, Kimi CLI, JetBrains IDEs, Claude and ChatGPT) and its tools](https://proxymail.qa/docs/mcp)+   - [Labs](https://proxymail.qa/docs/labs): features a person switches on in **Account settings → Labs** before they're available to everyone. Now: Marketing and offer emails (the Offers and Marketing areas, record_coupon_result, check_offers, mark_unsubscribed, mark_resubscribed, check_unsubscribe, record_consent, check_sequence and the coupon and marketing checks), and Spam score and attachment checks (spam_risk, harmful_attachment). API keys and agents follow their creator's switches; while o+ - [MCP server](https://api.proxymail.qa/mcp) (Streamable HTTP; signs in by browser, or an API key as bearer). Tools: get_project, create_address (an address with a persona, a date of birth for an age and a country if asked, a password for the sign-up form if asked, and the site and environment it's used on), form_values (what to type or pick in each field of a sign-up form, from what the page says about each), wait_for_code (kind: coupon for a coupon or promo code, with its discount and valid-un+ - Sign-in: an API key created by a signed-in person in **Project settings → API keys**, or OAuth (claude.ai, ChatGPT and other MCP clients sign in by browser and the person chooses a project). Available on the Free plan (60 requests a minute per key).+ - [AI sign-up page review](https://proxymail.qa/solve/ai-sign-up-page-review): an agent reviewing sign-up through to the verification email: check_email, count_emails, used and replaced links+ - [AI registration page review](https://proxymail.qa/solve/ai-registration-page-review): an agent testing every registration field with form_values and name, password and address variants+ - [Review a sign-up page by hand](https://proxymail.qa/solve/how-to-review-my-sign-up-page): a checklist for reviewing a sign-up page by hand, with Proxy Mail QA for Chrome for the test account and email+ - [Review a simple sign-up form](https://proxymail.qa/solve/review-a-simple-sign-up-form): twelve checks for a short email-and-password sign-up form+ - [Review a multi-page sign-up form](https://proxymail.qa/solve/review-a-multi-page-sign-up-form): a sign-up over several screens: form_values with the same address, Playwright, and by hand+ - [Review a financial sign-up form](https://proxymail.qa/solve/review-a-financial-website-sign-up-form): financial sign-ups: emails, exact ages and countries, awkward values; not SMS, KYC or payments+ - [An email address for testing registration](https://proxymail.qa/solve/email-for-checking-my-registration-form): a new email address for every registration test, compared with mail catchers and SMS services+ - [An email address for testing sign-in](https://proxymail.qa/solve/email-for-checking-my-sign-in-form): test accounts for sign-in forms: saved passwords, codes, magic links, password reset+ - [How long should a password be?](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be): NIST SP 800-63B rev 4 password length and rules, tested with get_password_variants+ - [No error for a password that breaks the rules](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors): a registration form that shows no error for passwords that break its rules: causes and a test+ - [Help me check my website](https://proxymail.qa/solve/help-me-check-my-website): a whole-website check, with free tools named for speed, accessibility, search and security+ - [Tools to build and check a website](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website): a toolkit by area for building and checking a website, most of it free+ - [What tools do I need for a website?](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website): the tools a website needs and which to skip+ - [Qoder](https://proxymail.qa/built-with/qoder)+ ## Guides: auth providers (the emails Supabase, Clerk, Auth0, Firebase, Auth.js, Better Auth and Amazon Cognito send, and their sending limits)+ - [Amazon Cognito](https://proxymail.qa/auth/cognito)

https://proxymail.qa/llms.txt

− - Create a random address on mailclub.dev (or the alternate domain enable.li, for apps that block one) in one click, or choose a custom name. Plus-addressing (name+tag@) is supported.− - Reports per project: a Dashboard (failed email checks, refused mail and failed runs; changes such as a new sending provider, a code where there was a link or links to a different site; how fast emails arrive; how many codes and links were used, replaced or expired first) and a QA report per date range (addresses, personas, notes, every email's code or link), as CSV or PDF; saved passwords only when chosen. QA reports flag addresses that share a saved password, without revealing it.− - Each code or link shows when it was used and by whom (opened or copied in the app, or fetched by an agent or test), and an older one shows when a newer email of the same kind replaced it.− - Runs: a CI job or agent session's evidence (addresses, which emails arrived and how fast, codes, link sites, checks, missing emails), with a Markdown report; the GitHub Action (aaquib90/proxymail-qa-action) posts it on the pull request. Kept 90 days.− - [Projects and teams](https://proxymail.qa/features/projects): what a project holds, setting one up, how API keys and agents reach one project, Team plan roles, reports, runs, the account pool, activity log and debug mode− - [Chrome extension](https://proxymail.qa/chrome-extension): fills sign-up forms and shows the code or link in the page− - Free: the whole product for individuals under fair use (up to 50 new addresses a day, around 500 incoming emails a day, 5 MB per message).− - Team ($5 a month or $45 a year per organisation, or $95 once for Lifetime; plus tax where it applies): an organisation with unlimited seats, per-project access (admins see every project), invites and member requests, and a shared activity log. Receiving on your own domain is planned for later.−   - [MCP server for each client (Claude Code, Cursor, GitHub Copilot, Antigravity, Codex, Claude and ChatGPT) and its tools](https://proxymail.qa/docs/mcp)−   - [Node client on npm: proxymail-qa](https://proxymail.qa/docs/node): npm install --save-dev proxymail-qa; ProxyMailQA with createAddress, waitForCode, waitForLink, messages, checkDelivery, variants, setPassword ([npm](https://www.npmjs.com/package/proxymail-qa))− - [REST API](https://api.proxymail.qa/v1) ([OpenAPI](https://api.proxymail.qa/v1/openapi.json)). Create an address, then GET /v1/addresses/{address}/code or /link waits up to 30 seconds and returns just the code or link, its kind, the sending service and expiry. When nothing arrives, the 404 (and the MCP tools' found: false answer) adds a hint: mail we refused for the address and why, or that nothing has reached it. GET /v1/addresses finds test accounts made earlier by tag, country, age (min_age− - [MCP server](https://api.proxymail.qa/mcp) (Streamable HTTP; signs in by browser, or an API key as bearer). Tools: get_project, create_address (an address with a persona, a date of birth for an age and a country if asked, a password for the sign-up form if asked, and the site and environment it's used on), form_values (what to type or pick in each field of a sign-up form, from what the page says about each), wait_for_code, wait_for_link (app: true for the link that opens a mobile app), list_ad+ - Create a random address on mailclub.dev (or the alternate domains enable.li and valida.te.it, for apps that block one) in one click, or choose a custom name. Plus-addressing (name+tag@) is supported.+ - Reports per project: a Dashboard by period and test area (failed email checks, mail refused or turned away and failed runs; changes such as a new sending provider, a code where there was a link or links to a different site; where emails would land; how fast emails arrive; how many codes and links were used, replaced or expired first) and a QA report for a period or a run (a verdict, what failed, what was tested, the runs, and every email's type, checks and code or link, with links shown withou+ - Each code or link shows when it was used and by whom (opened, copied or filled in the app or Proxy Mail QA for Chrome, or fetched by an agent or test), and an older one shows when a newer email of the same kind replaced it.+ - Runs: a CI job or agent session's evidence (addresses, which emails arrived and how fast, codes, link sites, checks, unsubscribe, offer and coupon checks, failed tests, missing emails), compared with the runs before it, with a Markdown report; the GitHub Action (aaquib90/proxymail-qa-action) posts it on the pull request, and a run's page prints it as a QA report. Kept 90 days.+ - [Projects and teams](https://proxymail.qa/features/projects): what a project holds, setting one up, how API keys and agents reach one project, Team plan roles, organisation and project logos and profile pictures, address limits by plan, reports, runs, the account pool, activity log and debug mode+ - [Marketing and offers](https://proxymail.qa/features/marketing): coupons and how fast they arrive, checkout results, offer reuse through address versions, unsubscribe watches, consent and marketing rules by country, marketing email checks, welcome series timing, harmful attachments and spam risk+ - [Deliverability](https://proxymail.qa/features/deliverability): the spam score out of 10 and its markers, harmful attachments, mail Cloudflare's mail servers turned away, SPF, DKIM and DMARC, size and layout checks, and the counts in Reports and run reports+ - [Chrome extension](https://proxymail.qa/chrome-extension): fills sign-up forms and shows the code or link in the page; in Labs, Offers and Marketing modes for coupons, the marketing box and unsubscribing+ - Free: the whole product for individuals, with 500 addresses in total (up to 50 a day), around 500 incoming emails a day under fair use, and 5 MB per message.+ - Team ($5 a month or $45 a year per organisation, or $95 once for Lifetime; plus tax where it applies): unlimited addresses (also in the owner's and admins' own spaces), an organisation with unlimited seats, per-project access (admins see every project), invites and member requests, and a shared activity log. Receiving on your own domain is planned for later.+   - [MCP server for each client (Claude Code, Cursor, GitHub Copilot, Antigravity, Codex, Windsurf, Zed, Kiro, OpenCode, Kilo Code, Roo Code, Augment Code, Trae, Mistral Vibe, Qwen Code, Kimi CLI, JetBrains IDEs, Claude and ChatGPT) and its tools](https://proxymail.qa/docs/mcp)+   - [Node client on npm: proxymail-qa](https://proxymail.qa/docs/node): npm install --save-dev proxymail-qa; ProxyMailQA with createAddress, waitForCode, waitForLink, messages, checkDelivery, variants, nameVariants, passwordVariants, setPassword ([npm](https://www.npmjs.com/package/proxymail-qa))+   - [Android apps with a coding agent](https://proxymail.qa/docs/android-agents): Claude Code, Codex or Cursor with adb, and Android Studio's Gemini agent+   - [Unusual names and passwords](https://proxymail.qa/docs/unusual-names-and-passwords): names with apostrophes, accents and other scripts, very long ones, HTML or SQL to store as text; passwords at a field's limits, each symbol class, spaces, non-ASCII, bcrypt's 72 bytes+   - [Labs](https://proxymail.qa/docs/labs): features a person switches on in Account settings → Labs before they're available to everyone. Now: Marketing and offer emails (the Offers and Marketing areas, record_coupon_result, check_offers, mark_unsubscribed, mark_resubscribed, check_unsubscribe, record_consent, check_sequence and the coupon and marketing checks), and Spam score and attachment checks (spam_risk, harmful_attachment). API keys and agents follow their creator's switches; while off, + - [REST API](https://api.proxymail.qa/v1) ([OpenAPI](https://api.proxymail.qa/v1/openapi.json)). Create an address, then GET /v1/addresses/{address}/code or /link waits up to 30 seconds and returns just the code or link, its kind, the sending service and expiry. When nothing arrives, the 404 (and the MCP tools' found: false answer) adds a hint: mail we refused for the address and why, or that nothing has reached it. GET /v1/addresses finds test accounts made earlier by tag, country, age (min_age+ - [MCP server](https://api.proxymail.qa/mcp) (Streamable HTTP; signs in by browser, or an API key as bearer). Tools: get_project, create_address (an address with a persona, a date of birth for an age and a country if asked, a password for the sign-up form if asked, and the site and environment it's used on), form_values (what to type or pick in each field of a sign-up form, from what the page says about each), wait_for_code (kind: coupon for a coupon or promo code, with its discount and valid-un+ - Docs search for agents without an account: the MCP server https://search.proxymail.qa/mcp (one tool, search), or POST https://search.proxymail.qa/search with {"query": "…"}. Signed-in MCP connections have it as search_docs. People can ask questions at https://proxymail.qa/ask+ - [How agents get access (auth.md)](https://proxymail.qa/auth.md): register with the person's email (auth.md service_auth: they sign in and type a 6-digit code the agent shows them), the MCP server's OAuth sign-in by browser, or an API key; no anonymous registration+ - WebMCP: in browsers that support it, every page of proxymail.qa offers the read-only tools search_docs, read_page (any page as Markdown) and get_agent_setup+ - What people ask: "Give me a test email for my staging sign-up and tell me the code when it arrives" (create_address, then wait_for_code; in a chat the person signs up with the address), "Why isn't my app's verification email arriving?" (check_delivery), "Check the password-reset email my app sent to my test address" (check_email), and, for agents that can use a browser, "Sign up on localhost:3000 with a new test account and confirm the email".+ - [Agent skills](https://proxymail.qa/skills): every skill we publish, for Claude Code, Cursor, Codex, GitHub Copilot, Qoder and other agents that read skills, each with its install command, file and ZIP. `npx skills add https://proxymail.qa` installs them from the site's index ([/.well-known/agent-skills/index.json](https://proxymail.qa/.well-known/agent-skills/index.json))+ - [Marketing email testing skill](https://proxymail.qa/.well-known/agent-skills/marketing-email-testing/SKILL.md) (needs Marketing and offer emails switched on in Labs): welcome coupons and checkout, one offer per person, unsubscribing that sticks, consent rules by country, welcome series timing and spam risk, on staging with test payments only+ - [Common Supabase sign-up and login problems](https://proxymail.qa/solve/supabase-auth-problems): missing emails, rate limits, expired and scanned links, PKCE in another browser, Database error saving new user+ - [Common Firebase sign-up and login problems](https://proxymail.qa/solve/firebase-auth-problems): no verification email, enumeration protection, emailVerified not updating, unauthorized-continue-uri, email-link sign-in, sign-up limits, emulator+ - [Sign-up and login problems in vibe-coded apps](https://proxymail.qa/solve/vibe-coded-login-problems): Lovable, Bolt, v0, Replit, Base44, Cursor, Claude Code: works only for you, preview links, missing callback and reset pages, swallowed errors+ - [Test coupon codes and welcome offers](https://proxymail.qa/solve/coupon-code-testing)+ - [Test unsubscribe links and one-click unsubscribe](https://proxymail.qa/solve/unsubscribe-testing)+ - [Test that a welcome offer can't be claimed twice](https://proxymail.qa/solve/welcome-offer-abuse)+ - [Marketing email rules by country (EU, UK, US, Canada, Australia, New Zealand, Switzerland, Japan, South Korea, Singapore, Hong Kong)](https://proxymail.qa/use-cases/marketing-rules-by-country)+ - [Welcome series and drip campaigns: order and timing](https://proxymail.qa/use-cases/drip-and-welcome-series)

https://proxymail.qa/llms.txt

− > Proxy Mail QA (https://proxymail.qa) gives QA testers and developers private, disposable, time-bound email addresses for testing sign-up, email verification, OTP, magic-link, password-reset and invite flows. When an email arrives, its verification code or link is extracted and shown ready to copy or click.− - Generated test personas (first name, last name, username), notes, tags and encrypted saved test passwords per address.− - QA reports per project and date range (addresses, personas, notes, every email's code or link), as CSV or PDF; saved passwords only when chosen. Reports flag addresses that share a saved password, without revealing it.− - An activity log of who created, revealed and deleted what, for owners and admins.− - Team (coming soon): an organisation with unlimited seats, per-project access (admins see every project), invites and member requests, and a shared activity log. Receiving on your own domain is planned for later.− - Guide: https://proxymail.qa/docs/api− - REST API: https://api.proxymail.qa/v1 (OpenAPI: https://api.proxymail.qa/v1/openapi.json). Create an address, then GET /v1/addresses/{address}/code or /link waits up to 30 seconds and returns just the code or link, its kind, the sending service and expiry. When nothing arrives, the 404 (and the MCP tools' found: false answer) adds a hint: mail we refused for the address and why, or that nothing has reached it. GET /v1/addresses/{address}/delivery checks an address at any time without waiting.− - MCP server: https://api.proxymail.qa/mcp (Streamable HTTP; signs in by browser, or an API key as bearer). Tools: get_project, create_address (an address with a persona, and a password for the sign-up form if asked), wait_for_code, wait_for_link, list_addresses, update_address, delete_address.− - Setup to paste into Claude Code, Cursor, GitHub Copilot or another agent: https://proxymail.qa/docs/api#agent-setup− - Proxy Mail QA for Chrome (coming soon, free on every plan): a browser extension for testing sign-ups by hand. On test sites the tester turns it on for, one click fills a test address, name, username and password into the sign-up form; after submitting it asks to save the password to the address; the code or link appears in the page with Fill, Copy or Open. https://proxymail.qa/chrome-extension− - Agent skill: https://proxymail.qa/.well-known/agent-skills/proxymail-qa/SKILL.md− - Security: how data and passwords are protected end to end (test accounts only, AES-256-GCM for saved test passwords, row-level security, retention, what isn't built yet): https://proxymail.qa/security− - How to use Proxy Mail QA, step by step (create an account, create a test address, use it, copy the code or click the link, read the full email, saved passwords and personas, clean-up): https://proxymail.qa/getting-started− - Test email not arriving? Usual causes, email providers in sandbox or test mode and their fixes, and what we refuse: https://proxymail.qa/troubleshooting (send Accept: text/markdown, or add .md, for a Markdown copy)− - Test sign-up and email verification: https://proxymail.qa/solve/email-verification-testing− - Test OTP and one-time login codes: https://proxymail.qa/solve/otp-code-testing− - Test magic links and passwordless sign-in: https://proxymail.qa/solve/magic-link-testing− - Test password reset emails: https://proxymail.qa/solve/password-reset-testing− - Stop sharing one Gmail inbox for QA: https://proxymail.qa/solve/shared-test-inbox− - Take QA notes on each test account by voice with Wispr Flow: https://proxymail.qa/solve/voice-notes-wispr-flow− - Verification link points to localhost:3000 (fixes for Supabase, Lovable, Firebase, Auth.js, Rails, Django, Laravel): https://proxymail.qa/solve/localhost-links− - Age gates and age-restricted content (one account per age band, parental consent emails): https://proxymail.qa/use-cases/age-restricted-content− - Content that depends on location (geo-blocking, regional prices, tax, consent): https://proxymail.qa/use-cases/location-based-content− - Predictor game and fantasy league scoring (a player per scoring rule, tie-breaks, results emails): https://proxymail.qa/use-cases/predictor-games− - Membership tiers, paywalls and free trials: https://proxymail.qa/use-cases/membership-tiers− - Roles and permissions, including across customers: https://proxymail.qa/use-cases/roles-and-permissions− - Ticket ballots and prize draws: https://proxymail.qa/use-cases/ballots-and-prize-draws− - Referral rewards and welcome offers, including abuse rules: https://proxymail.qa/use-cases/referrals-and-welcome-offers− - Both sides of a marketplace: https://proxymail.qa/use-cases/marketplaces− - Email changes, lockouts and account deletion: https://proxymail.qa/use-cases/account-changes− - Email preferences, consent and unsubscribe: https://proxymail.qa/use-cases/email-preferences− - Claude Code: https://proxymail.qa/built-with/claude-code− - OpenAI Codex: https://proxymail.qa/built-with/codex− - Replit: https://proxymail.qa/built-with/replit− - Lovable: https://proxymail.qa/built-with/lovable− - Base44: https://proxymail.qa/built-with/base44− - Bolt: https://proxymail.qa/built-with/bolt− - Cursor: https://proxymail.qa/built-with/cursor− - All tools at a glance: https://proxymail.qa/compare− - Proxy Mail QA vs Mailinator: https://proxymail.qa/compare/mailinator+ > [Proxy Mail QA](https://proxymail.qa) gives QA testers and developers private, disposable, time-bound email addresses for testing sign-up, email verification, OTP, magic-link, password-reset and invite flows. When an email arrives, its verification code or link is extracted and shown ready to copy or click.+ - Generated test personas (first name, last name, username, and a date of birth for an age band: adult, 21+, under 18, under 15, under 13, any age, turning 18 tomorrow or today; and a country, as an ISO code such as GB), notes, tags and encrypted saved test passwords per address.+ - Reports per project: a Dashboard (failed email checks, refused mail and failed runs; changes such as a new sending provider, a code where there was a link or links to a different site; how fast emails arrive; how many codes and links were used, replaced or expired first) and a QA report per date range (addresses, personas, notes, every email's code or link), as CSV or PDF; saved passwords only when chosen. QA reports flag addresses that share a saved password, without revealing it.+ - Each code or link shows when it was used and by whom (opened or copied in the app, or fetched by an agent or test), and an older one shows when a newer email of the same kind replaced it.+ - Runs: a CI job or agent session's evidence (addresses, which emails arrived and how fast, codes, link sites, checks, missing emails), with a Markdown report; the GitHub Action (aaquib90/proxymail-qa-action) posts it on the pull request. Kept 90 days.+ - An account pool: tests check out an account in a known state (by tags, country, age or saved password) that no other test has, and return it, recording its new state.+ - An activity log of who created, used, revealed and deleted what, and how (the app, the Chrome extension, an agent or an API key), with a filter, for owners and admins.+ ## Feature pages+ - [Inbox dashboard](https://proxymail.qa/features/dashboard): the Accounts view, row by row, what each test account keeps, filters, search and the safe inbox view, with an interactive demo+ - [Projects and teams](https://proxymail.qa/features/projects): what a project holds, setting one up, how API keys and agents reach one project, Team plan roles, reports, runs, the account pool, activity log and debug mode+ - [Tests and CI](https://proxymail.qa/features/tests): the npm package, the Python helper and the REST API in end-to-end tests, the GitHub Action's report on the pull request, the account pool for parallel tests and the email checks+ - [AI agents](https://proxymail.qa/features/agents): how coding agents sign up and get the code themselves, what they can do, and why they need no database keys+ - [Chrome extension](https://proxymail.qa/chrome-extension): fills sign-up forms and shows the code or link in the page+ - [MCP server and plugins](https://proxymail.qa/features/mcp): connecting each client, the tools, browser sign-in and security, the Claude Code plugin, the Cursor Directory listing (https://cursor.directory/plugins/proxymail-qa), the agent skill and the MCP Registry listing+ - Team ($5 a month or $45 a year per organisation, or $95 once for Lifetime; plus tax where it applies): an organisation with unlimited seats, per-project access (admins see every project), invites and member requests, and a shared activity log. Receiving on your own domain is planned for later.+ - [Developer docs](https://proxymail.qa/docs) (every page has a Markdown copy: add .md, or send Accept: text/markdown)+   - [API and MCP server, with the one-prompt agent setup](https://proxymail.qa/docs/api)+   - [MCP server for each client (Claude Code, Cursor, GitHub Copilot, Antigravity, Codex, Claude and ChatGPT) and its tools](https://proxymail.qa/docs/mcp)+   - [REST API](https://proxymail.qa/docs/rest-api): waiting, counting emails and checking that none arrive, email checks, runs, the account pool, dates of birth, errors+   - [REST API reference, generated from the OpenAPI description](https://proxymail.qa/docs/reference)+   - [Node client on npm: proxymail-qa](https://proxymail.qa/docs/node): npm install --save-dev proxymail-qa; ProxyMailQA with createAddress, waitForCode, waitForLink, messages, checkDelivery, variants, setPassword ([npm](https://www.npmjs.com/package/proxymail-qa))+   - [Playwright](https://proxymail.qa/docs/playwright)+   - [Cypress](https://proxymail.qa/docs/cypress)+   - [Puppeteer](https://proxymail.qa/docs/puppeteer)+   - [Python](https://proxymail.qa/docs/python): pytest with Selenium or Playwright for Python; a standard-library helper+   - [Running in CI](https://proxymail.qa/docs/ci): API key as a secret, one address per run with plus-tags, parallel workers, Claude Code GitHub Action, Copilot coding agent, Codex+   - [API keys](https://proxymail.qa/docs/api-keys)+   - [Mobile apps](https://proxymail.qa/docs/mobile): Maestro, XCUITest, Espresso, Flutter, Detox and Appium helpers that create addresses, wait for codes and links, check and count emails, sign in as saved accounts or borrow pooled ones, and join CI run reports; opening links on simulators and emulators+   - [iOS apps with a coding agent](https://proxymail.qa/docs/ios-agents): Claude Code Desktop's iOS Simulator pane, Xcode's tools through xcrun mcpbridge, Xcode's own agents+   - [Unusual email addresses](https://proxymail.qa/docs/unusual-addresses): variants that still reach the inbox: capitals, plus tags with special characters, 64-character names; and invalid ones for testing rejection+   - [Limits and safety](https://proxymail.qa/docs/limits)+ - [REST API](https://api.proxymail.qa/v1) ([OpenAPI](https://api.proxymail.qa/v1/openapi.json)). Create an address, then GET /v1/addresses/{address}/code or /link waits up to 30 seconds and returns just the code or link, its kind, the sending service and expiry. When nothing arrives, the 404 (and the MCP tools' found: false answer) adds a hint: mail we refused for the address and why, or that nothing has reached it. GET /v1/addresses finds test accounts made earlier by tag, country, age (min_age+ - [MCP server](https://api.proxymail.qa/mcp) (Streamable HTTP; signs in by browser, or an API key as bearer). Tools: get_project, create_address (an address with a persona, a date of birth for an age and a country if asked, a password for the sign-up form if asked, and the site and environment it's used on), form_values (what to type or pick in each field of a sign-up form, from what the page says about each), wait_for_code, wait_for_link (app: true for the link that opens a mobile app), list_ad+ - [Setup to paste into Claude Code, Cursor, GitHub Copilot or another agent](https://proxymail.qa/docs/api#agent-setup)+ - [Proxy Mail QA for Chrome](https://proxymail.qa/chrome-extension): free on every plan ([Chrome Web Store](https://chromewebstore.google.com/detail/proxy-mail-qa-for-chrome/pjfkhpfocjfhlddallkabnoobadikbad)). A browser extension for testing sign-ups by hand. On test sites the tester turns it on for, one click fills a test address, name, username, date of birth and password into the sign-up form; after submitting it asks to save the password to the address; the code or link appears in the page w+ - [Agent skill](https://proxymail.qa/.well-known/agent-skills/proxymail-qa/SKILL.md)+ - [Auth regression pack skill](https://proxymail.qa/.well-known/agent-skills/auth-regression-pack/SKILL.md): the same checks of sign-up, reset and invitation emails and links every time, including link reuse, with a report of what changed since the last run+ - [Security: how data and passwords are protected end to end](https://proxymail.qa/security): test accounts only, AES-256-GCM for saved test passwords, row-level security, retention, what isn't built yet+ - [How to use Proxy Mail QA, step by step](https://proxymail.qa/getting-started): create an account, create a test address, use it, copy the code or click the link, read the full email, saved passwords and personas, clean-up+ - [Test email not arriving? Usual causes, email providers in sandbox or test mode and their fixes, and what we refuse](https://proxymail.qa/troubleshooting) (send Accept: text/markdown, or add .md, for a Markdown copy)

Showing the first 40 of each.