MailMCP
PYPI · MCPPRODUCTS-MAIL
Read, search and draft email over IMAP from any AI agent. Never sends.
Available components
Last scanned (2 hours ago)
Scores higher than 61% 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 Security100
- No malware found by supply-chain analysis.Pass
- 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
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 8 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability53
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 278 tokens (~46/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Oct 26 41
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 24 Oct 2026 · Analysed pypi/mcpproducts-mail@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
cloud_digest ~33
PREMIUM (needs MPX_API_KEY): cloud inbox digest — summarised daily email brief.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
draft_email ~59
Create a DRAFT (appended to Drafts folder). This server never sends — the human reviews and sends.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| cc | string | – | – |
| subject | string | yes | – |
| to | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_recent ~33
Latest email headers from a folder (default INBOX).
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
move_email ~44
Move a message to another folder (e.g. Archive, Junk).
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | – |
| num | string | yes | – |
| to_folder | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
read_email ~41
Read one message by sequence number (from list_recent/search): full text body + attachment names.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | – |
| num | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_emails ~68
IMAP search. field: FROM | TO | SUBJECT | BODY | TEXT (any). since_days limits age.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | – |
| folder | string | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| since_days | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the MailMCP MCP server?
MailMCP runs locally as a PyPI package, launched with uvx mcpproducts-mail. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcpproducts-mail
claude mcp add com-mcpproducts-mail -- uvx mcpproducts-mail
What is the MailMCP MCP server?
MailMCP is an MCP server listed in the public MCP registry as com.mcpproducts/mail. Read, search and draft email over IMAP from any AI agent. Never sends. This page covers its PyPI package (mcpproducts-mail).
Is the MailMCP MCP server safe to use?
MailMCP scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 October 2026. 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 MailMCP MCP server expose?
MailMCP exposes 6 tools: list_recent, search_emails, read_email, draft_email, move_email, cloud_digest. Their descriptions and schemas cost roughly 278 tokens of context every time the server is loaded.
Is the MailMCP MCP server still maintained?
MailMCP is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.