A powerful MCP server for sending emails via 126.com SMTP service. Perfect for AI assistants and automation workflows!
Free
Nothing to run from here
Mailagent is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MailAgent MCP server (stdio) for Cursor and AI agents — email verification inboxes
Quickstart
# 1 — run it from where its publisher ships it
npx -y @mailagent/mcp
# 2 — the plan is chosen at checkout, in the browser
# 3 — ask your agent something
> MailAgent MCP server (stdio) for Cursor and AI agents — email verification inboxes
Publishernot claimed
ALAll 1 server
alex0nder1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Mailagent as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add mailagent-mcp -- npx -y @mailagent/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
This is a paid listing, so the CLI has to be signed in and the licence has to be on your account — how the login works. Until then the install stops with the price rather than half-writing a config entry.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
37 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Issue a short-lived scoped API key for one autonomous MailAgent run. Requires an unrestricted DB team key.
Takes no parameters.
Example callreturns →
Autopilot planner: return the next best MailAgent tool and ready payloads from current signup/login state. Use when unsure what to do next.
Takes no parameters.
Example callreturns →
Start a server-side autonomous agent run session and return the first autopilot plan.
Takes no parameters.
Example callreturns →
Resume an agent run and return the next best tool/payload from saved session state.
Takes no parameters.
Example callreturns →
Report run progress/failure, append a timeline step, update saved state, and return the next plan.
Takes no parameters.
Example callreturns →
Workspace Agent preview: summarize supplied mail/thread messages, action items, decisions, and open questions.
Takes no parameters.
Example callreturns →
Workspace Agent preview: draft a reply from supplied messages. Draft-only; never sends.
Takes no parameters.
Example callreturns →
Workspace Agent preview: suggest reminders/follow-ups from supplied messages. Does not create reminders yet.
Takes no parameters.
Example callreturns →
Workspace Agent preview: persist a reminder/follow-up. Does not send email or create calendar events.
Takes no parameters.
Example callreturns →
Workspace Agent preview: list saved reminders/follow-ups for the current team or API key.
Takes no parameters.
Example callreturns →
Workspace Agent preview: mark a saved reminder/follow-up as completed.
Takes no parameters.
Example callreturns →
Workspace Agent preview: log what the agent did for a reminder/thread.
Takes no parameters.
Example callreturns →
Workspace Agent preview: list logged Workspace actions, optionally scoped by reminderId or threadId.
Takes no parameters.
Example callreturns →
Read the Workspace Agent autonomy policy. Default is draft_only.
Takes no parameters.
Example callreturns →
Show DeepSeek/Qwen readiness and fallback order without exposing secrets.
Takes no parameters.
Example callreturns →
Admin-only: configure policy-gated autonomous replies.
Takes no parameters.
Example callreturns →
Policy-gated autonomous reply from a real inbound message. Use dryRun first; idempotencyKey is required to send.
Takes no parameters.
Example callreturns →
Suggest service preset, expectFrom, subjectContains, flow, and snippets from a sample auth email From/Subject/body. Use before verify when sender or service is unclear.
Takes no parameters.
Example callreturns →
Create a temporary email inbox for agent workflows (signups, OTP, magic links). Returns inbox id and email address to use on external forms.
Takes no parameters.
Example callreturns →
Preferred agent flow: create inbox (or reuse inboxId), wait for verification email, return agent.primaryAction with OTP or magic link and clear instruction. Use service preset (github, google, dribbble, …).
Takes no parameters.
Example callreturns →
One-shot agent flow: optionally create inbox, wait via SSE for first allowed email, return OTP + links, delete inbox by default. Use service=dribbble for Dribbble signup.
Takes no parameters.
Example callreturns →
List active inboxes by label (QA: debug failed CI run, find address/ids).
Takes no parameters.
Example callreturns →
Block until the first email arrives (SSE, fallback poll). Use after submitting a form to the inbox address.
Takes no parameters.
Example callreturns →
List all messages received for an inbox (newest first).
Takes no parameters.
Example callreturns →
Get OTP code and links from the latest email in the inbox (pre-parsed at ingest). Best after a message arrived.
Takes no parameters.
Example callreturns →
Inject test OTP email without SMTP (QA/dev, sim_* provider).
Takes no parameters.
Example callreturns →
Send outbound email from inbox (two-way agent mail).
Takes no parameters.
Example callreturns →
List threads or messages in a thread.
Takes no parameters.
Example callreturns →
When wait/verify fails: messages, callbacks, hints, debugUiUrl, troubleshooting.
Takes no parameters.
Example callreturns →
Get inbox status: address, expiry, message count.
Takes no parameters.
Example callreturns →
Delete inbox and all messages early (cleanup after verification).
Takes no parameters.
Example callreturns →
Delete all inboxes matching a labelPrefix, or an agent run via runId.
Takes no parameters.
Example callreturns →
Download archived .eml metadata or body (base64 via API when includeBody). Use when extract finds no OTP.
Takes no parameters.
Example callreturns →
Check email syntax, disposable, role, MX (DNS). ONLY for app validation tests — NOT before verify_signup.
Takes no parameters.
Example callreturns →
Read multi-step agent run state (JSON + step log) by runId.
Takes no parameters.
Example callreturns →
Read normalized agent run timeline events by runId.
Takes no parameters.
Example callreturns →
Merge state and/or append a step for multi-step agent flows.
Takes no parameters.
Example callreturns →
Startermost installed
$19 / month
- 15,000 calls a month, included
- 180 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Growth
$49 / month
- 75,000 calls a month, included
- 900 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
Scale
$99 / month
- 300,000 calls a month, included
- 3,600 calls a minute at peak
- Every tool the listing has
- Cancel any time — the unused days are credited
- Runs behind the gateway, so cancelling stops it
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
No call is billed on its own, and this plan carries no monthly call limit. $19 a month covers every tool at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 97 / 100
Release 0.2.16 · scanned 25 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest081ac16cc87d804a971784083436a675849eb05617f37442991639b504560048
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (37 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| mailagent_issue_access | no tags | |
| mailagent_plan_next | no tags | |
| mailagent_start_run | no tags | |
| mailagent_next_run | no tags | |
| mailagent_report_run | no tags | |
| mailagent_workspace_summarize | untrusted-input | |
| mailagent_workspace_draft_reply | no tags | |
| mailagent_workspace_suggest_reminders | no tags | |
| mailagent_workspace_create_reminder | external-sink | |
| mailagent_workspace_list_reminders | no tags | |
| mailagent_workspace_complete_reminder | no tags | |
| mailagent_workspace_log_action | no tags | |
| mailagent_workspace_list_actions | no tags | |
| mailagent_workspace_get_policy | no tags | |
| mailagent_workspace_model_status | no tags | |
| mailagent_workspace_set_policy | no tags | |
| mailagent_workspace_execute_reply | no tags | |
| mailagent_suggest_preset | no tags | |
| mailagent_create_inbox | no tags | |
| mailagent_verify_signup | no tags | |
| mailagent_wait_and_extract | no tags | |
| mailagent_list_inboxes | no tags | |
| mailagent_wait_for_message | no tags | |
| mailagent_list_messages | no tags | |
| mailagent_extract_verification | no tags | |
| mailagent_simulate_message | no tags | |
| mailagent_send_message | external-sink | |
| mailagent_list_threads | no tags | |
| mailagent_diagnose_inbox | no tags | |
| mailagent_get_inbox | no tags | |
| mailagent_delete_inbox | no tags | |
| mailagent_cleanup_inboxes | no tags | |
| mailagent_get_raw_message | untrusted-input | |
| mailagent_check_email | no tags | |
| mailagent_get_run_session | no tags | |
| mailagent_get_run_timeline | no tags | |
| mailagent_patch_run_session | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest081ac16cc87d804a
Scanned2026-08-25
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 0.2.16 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.2.16
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Mailagent in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.