mcp-email-server
PyPI
v1.6.2
Published by wh1isper — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
IMAP and SMTP via MCP Server
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`dev/build_frontend.py:160`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: the frontend") subprocess.run([npm, "ci"], cwd=FRONTEND, check=True) # noqa: S603 - maintainer tool su
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dev/build_frontend.py
In the server's implementation (`dev/verify_container.py:35`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ess[str]: process = subprocess.run( # noqa: S603 - fixed Docker executable with maintainer-supplied image tag
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dev/verify_container.py
In a packaging/dev/install script (shipped, but not the server runtime) (`frontend/e2e/local-management.spec.ts:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from 'node:child_process' import { chmodSync, mkdtempSync, rmSync, writeFileSync } from 'node:fs' import {
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server frontend/e2e/local-management.spec.ts
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/e2e/test_stdio_greenmail.py:298`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: -> str: completed = subprocess.run( # noqa: S603 - fixed installed script with test-owned arguments [str(co
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/e2e/test_stdio_greenmail.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_packaging.py:46`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: try: process = subprocess.Popen( # noqa: S603 - exact test-owned executable and arguments command,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/test_packaging.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_stdio_protocol.py:265`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ndle: process = subprocess.Popen( # noqa: S603 - exact test-owned executable and arguments [str(exe
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/test_stdio_protocol.py
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_windows_security.py:81`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: .Popen[str]: return subprocess.Popen( # noqa: S603 - fixed current interpreter and test-owned script [sys.e
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/test_windows_security.py
Each tool and what it can reach — statically extracted from the published source.
list_mailboxesno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.6.2 latest |
A 93/100 | 7 | 1.13.0 | 2026-09-05 |
v1.6.1 |
A 93/100 | 6 | 1.13.0 | 2026-09-04 |
v1.5.2 |
A 93/100 | 6 | 1.13.0 | 2026-08-29 |
v1.5.1 |
A 93/100 | 6 | 1.13.0 | 2026-08-27 |
v1.4.2 |
A 93/100 | 6 | 1.13.0 | 2026-08-25 |
v1.4.1 |
A 93/100 | 6 | 1.12.1 | 2026-08-09 |
v1.3.2 |
A 93/100 | 6 | 1.12.1 | 2026-08-06 |
v1.3.1 |
A 93/100 | 6 | 1.12.1 | 2026-08-04 |
v1.1.1 |
A 93/100 | 5 | 1.12.1 | 2026-08-02 |
v1.1.0 |
A 93/100 | 5 | 1.12.1 | 2026-07-31 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-email-server --online --registry pypi
Independent packages implementing the same tool, scanned with the same engine. Compare all 20 side by side →
MCP server for email via IMAP/SMTP — read, search, send, and manage emails
MCP server for Gmail operations
Universal mailbox MCP server with automatic provider configuration and mail sending for services such as QQ Mail, 163, Outlook, and corporate email.
MCP server for Blip disposable email — create inboxes, receive emails, extract OTP codes
MCP server for the Vorlek API — email tools, catalog discovery, and operation lookup across SendGrid, Mailchimp, and Klaviyo.
通用邮箱MCP服务器 - 支持QQ、163、Gmail(由于谷歌政策不支持OAuth2.0,所以无法使用)、Outlook、企业邮箱等多种邮箱服务商的自动配置和邮件发送功能
One key, 100+ models — chat with any LLM and generate video, images, speech. Free trial at 370.ai.
Retired compatibility stub for the AgentCanary MCP server. Daily briefs continue on X and Telegram.
A Backstage plugin that provides a chat interface for interacting with the MCP Servers.
Signal-first Bitcoin intelligence: sovereign, hiring & hashrate signals over MCP.
WhatsApp® reminders and rescheduling for Calendly. Public read-only MCP endpoint.
Open Source Generic MCP Client for testing & evaluating mcp servers and agents