Back to MCP Trust Indexm8ven
52
/ 100
1 month ago
glama

Mail MCP Server

Enables AI assistants to send, read, and manage emails via SMTP and IMAP, with support for attachments, threads, and mailbox organization.

→ martinzarfl/mail-mcp· listed on glama
Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find.

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: IMAP_PASS, OAUTH_CLIENT_SECRET, SMTP_PASS
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies4 high1 medium6 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.0.4GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.0.4GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highnodemailer@6.9.15GHSA-p6gq-j5cr-w38f

Nodemailer: Message-level raw option bypasses disableFileAccess/disableUrlAccess, enabling arbitrary file read and full-response SSRF in the delivered message

highnodemailer@6.9.15GHSA-rcmh-qjqh-p98v

Nodemailer’s addressparser is vulnerable to DoS caused by recursive calls

mediumnodemailer@6.9.15GHSA-mm7p-fcc7-pg87

Nodemailer: Email to an unintended domain can occur due to Interpretation Conflict

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configAUTH_HOST
configAUTH_PORT
configAUTH_REALM
configHOST
configIMAP_HOST— export ="imap.gmail.com" # IMAP server (defaults to SMTP_HOST)
🔐 secretIMAP_PASS— export ="your-app-password" # IMAP password (defaults to SMTP_PASS)
configIMAP_PORT— export ="993" # IMAP port (default: 993)
configIMAP_TLS— export ="true" # Use TLS (default: true)
configIMAP_USER— export ="your-email@gmail.com" # IMAP username (defaults to SMTP_USER)
configOAUTH_CLIENT_ID
🔐 secretOAUTH_CLIENT_SECRET
configPORT— TRANSPORT=sse =8080 npm run dev:sse:env
configSMTP_FROM— export ="your-email@gmail.com" # (Optional) Default sender address
configSMTP_HOST— export ="smtp.gmail.com" # SMTP server hostname
🔐 secretSMTP_PASS— export ="your-app-password" # SMTP password
configSMTP_PORT— export ="587" # SMTP server port (587 or 465)
configSMTP_SECURE— export ="false" # (Optional) Use TLS (true for port 465)
configSMTP_USER— export ="your-email@gmail.com" # SMTP username
configSSE_PATH— /sse - SSE endpoint path (default: /sse)
configTRANSPORT— sse npm run dev:sse:env
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/martinzarfl-mail-mcp-12dlyv)](https://m8ven.ai/mcp/martinzarfl-mail-mcp-12dlyv)
commit: 7271c46442b7562bfaa7b8ffe8f13f8d40ab0dff
code hash: 70a83621f10d2ce8158f913c846ff5e878fad7342847a82d599dee7ac5d1b249
verified: 6/23/2026, 10:34:15 AM
view raw JSON →