NetEase Mail
PYPI · NETEASE-MAIL-MCP-SERVER
NetEase personal mail (163/126/yeah.net/188): search, read, draft, send with confirmation.
Available components
Last scanned (22 hours ago)
Scores higher than 59% of PyPI servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 3 of 42 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SeraFxy/netease-mail-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1817 tokens (~181/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 72% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/netease-mail-mcp-server@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | SeraFxy/netease-mail-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SeraFxy/netease-mail-mcp/.github/workflows/release.yml@refs/tags/v0.1.1 |
| Rekor log index | 3560604815 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:f2525f399fe98ad21e6f6f9afb5926e3ce3510fae63cab16c708601ecfe7a074 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 42 packages
| Packages resolved | 42 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_draft ~295
Save an email to Drafts (草稿箱) without sending; the user can review it in their mail app. Supports replies (reply_to_id, reply_all: Re: subject, In-Reply-To/References, recipients from the original) and forwards (forward_id). Returns draft_id + preview.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Email address; omit for the default (first) account. |
| attachments | – | – | Absolute local file paths (≤10, ≤20 MB total). Hidden files under home, ~/Library (iCloud Drive and cloud drives excepted), %APPDATA%, /etc and similar are refused; NETEASE_MAIL_ATTACHMENT_ROOTS can… |
| bcc | – | – | Addresses: "a@x.com, Name <b@y.com>" or a list. |
| body | string | – | Plain-text body. |
| cc | – | – | Addresses: "a@x.com, Name <b@y.com>" or a list. |
| forward_id | – | – | Forward this message. |
| forward_mode | string | – | – |
| html_body | – | – | Optional HTML alternative. |
| quote_original | boolean | – | Quote the original in replies. |
| reply_all | boolean | – | – |
| reply_to_id | – | – | Reply to this message (sets threading headers). |
| subject | – | – | Defaults to Re:/Fwd: original. |
| to | – | – | Addresses: "a@x.com, Name <b@y.com>" or a list. |
No output schema declared.
No examples provided.
download_attachment ~145
Save one attachment into the download dir (NETEASE_MAIL_DOWNLOAD_DIR) or a subdirectory of it: sanitized name, never overwrites or follows links, file mode 0600, marked as downloaded (macOS quarantine / Windows Zone.Identifier), ≤50 MB. Returns path, size, sha256, content_type, and a text excerpt for text/csv/json/md files.
| Name | Type | Req | Description |
|---|---|---|---|
| dest_dir | – | – | Subdirectory of the download dir to save into (relative, or an absolute path inside it). Anything outside the download dir is refused. |
| filename | – | – | Or the attachment filename. |
| id | string | yes | Message id. |
| index | – | – | Attachment index from read_message. |
No output schema declared.
No examples provided.
get_thread ~67
Reconstruct the conversation around a message across its folder, INBOX and Sent, using Message-ID/In-Reply-To/References (subject as fallback). Chronological, with snippets.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Any message id in the conversation. |
| max_messages | integer | – | ≤50 |
No output schema declared.
No examples provided.
list_accounts ~54
List configured NetEase accounts, the default account, the mode (readonly/draft/full) and whether a 授权码 is stored. check=true also logs in and reports INBOX counts.
| Name | Type | Req | Description |
|---|---|---|---|
| check | boolean | – | – |
No output schema declared.
No examples provided.
list_folders ~78
List folders with decoded names (e.g. 草稿箱, 已发送), raw IMAP names and special-use role (inbox/drafts/sent/trash/junk). with_counts=true adds message/unseen counts.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Email address; omit for the default (first) account. |
| with_counts | boolean | – | – |
No output schema declared.
No examples provided.
manage_messages ~106
Move, trash, mark read/unread or flag/unflag up to 50 messages. mark/flag run immediately (reversible). move/trash are two-phase like send_email: preview + human approval (elicitation or confirmation_token). trash moves to 已删除; nothing is ever permanently deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| confirmation_token | – | – | – |
| ids | array | yes | Message ids (≤50). |
| target_folder | – | – | For move: folder name/role. |
No output schema declared.
No examples provided.
read_message ~119
Read one message: headers (incl. Message-ID/In-Reply-To/References), text body (plain preferred, HTML converted to text), attachment list [{index, filename, content_type, size}] and flags. Does not mark the message read unless mark_read=true.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Message id from search_messages. |
| include_html | boolean | – | – |
| mark_read | boolean | – | Also mark as read (needs mode draft/full). Default: unchanged. |
| max_chars | integer | – | Body chars to return (≤100000). |
No output schema declared.
No examples provided.
search_messages ~289
Search or list messages newest-first. Returns ids plus date/from/to/subject/flags. Date and unread/flagged filters run on the server; query/from/to/subject match headers locally over at most max_scan candidates (truncated=true means more may exist). Message bodies are never searched.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Email address; omit for the default (first) account. |
| before | – | – | YYYY-MM-DD, exclusive. |
| flagged | – | – | true = flagged (starred) only |
| folder | – | – | Folder name/role ("INBOX", "已发送", "sent"), a list, or "all" (every folder except Junk/Trash/病毒文件夹). |
| from | – | – | Substring of the sender's display name or address. Display names are set by the sender and can imitate an address; check the address itself. |
| has_attachment | – | – | – |
| limit | integer | – | Max results (≤100). |
| max_scan | integer | – | Max candidates to check client-side (≤5000). |
| query | – | – | Words that must all appear in From/To/Cc/Subject (case-insensitive substring). Bodies are not searchable. |
| since | – | – | YYYY-MM-DD, inclusive. |
| subject | – | – | Substring of the subject. |
| to | – | – | Substring of a To/Cc name/address. |
| unread | – | – | true = unread only, false = read only |
No output schema declared.
No examples provided.
send_email ~267
Send an email via SMTP (same arguments as create_draft, or draft_id to send a saved draft). Two-phase: the first call returns a full preview and asks the human (MCP elicitation) or returns confirmation_token; call again with the token ONLY after the user explicitly approves. Any change to recipients/subject/body/attachments → rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Email address; omit for the default (first) account. |
| attachments | – | – | – |
| bcc | – | – | Addresses: "a@x.com, Name <b@y.com>" or a list. |
| body | string | – | – |
| cc | – | – | Addresses: "a@x.com, Name <b@y.com>" or a list. |
| confirmation_token | – | – | From the preview response, after the user approved. |
| delete_draft_after_send | boolean | – | – |
| draft_id | – | – | Send this draft exactly as saved (other content arguments must be omitted). |
| forward_id | – | – | – |
| forward_mode | string | – | – |
| html_body | – | – | – |
| quote_original | boolean | – | – |
| reply_all | boolean | – | – |
| reply_to_id | – | – | – |
| subject | – | – | – |
| to | – | – | Addresses: "a@x.com, Name <b@y.com>" or a list. |
No output schema declared.
No examples provided.
wait_for_message ~213
Wait for a NEW message (arriving after the call starts) matching from/subject/query, e.g. a sign-up verification email. Returns the summary plus `codes`: likely verification codes from subject/body. Uses IDLE when available, else polling.
| Name | Type | Req | Description |
|---|---|---|---|
| account | – | – | Email address; omit for the default (first) account. |
| folder | string | – | – |
| from | – | – | Sender's email address: a full address matches exactly ('noreply@github.com'), '@github.com' matches that domain and its subdomains, anything else is a substring of the address ('github'). Display na… |
| lookback_s | integer | – | Also accept messages that arrived up to this many seconds before the call (0 = only new mail). |
| poll_s | integer | – | Polling interval when IDLE is unavailable. |
| query | – | – | Words in From/To/Cc/Subject. |
| subject | – | – | Subject substring. |
| timeout_s | integer | – | ≤600 |
No output schema declared.
No examples provided.
How do I install the NetEase Mail MCP server?
NetEase Mail runs locally as a PyPI package, launched with uvx netease-mail-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · netease-mail-mcp-server
claude mcp add serafxy-netease-mail-mcp -- uvx netease-mail-mcp-server
What is the NetEase Mail MCP server?
NetEase Mail is an MCP server listed in the public MCP registry as io.github.SeraFxy/netease-mail-mcp. NetEase personal mail (163/126/yeah.net/188): search, read, draft, send with confirmation. This page covers its PyPI package (netease-mail-mcp-server).
Is the NetEase Mail MCP server safe to use?
NetEase Mail scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the NetEase Mail MCP server expose?
NetEase Mail exposes 10 tools: list_accounts, list_folders, search_messages, read_message, get_thread, and 5 more. Their descriptions and schemas cost roughly 1,633 tokens of context every time the server is loaded.
Is the NetEase Mail MCP server still maintained?
NetEase Mail is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the NetEase Mail MCP server under?
NetEase Mail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.