Email (weiting-tw) MCP Server
mcp-email
PyPI
v0.5.0
Published by weiting-tw — 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/SMTP 信箱 MCP server — 把任意標準信箱（Gmail/Outlook/自架…）包成 MCP tools；支援本地 stdio 與遠端 HTTP/OAuth 部署
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 − 4 = 96. 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 |
|---|---|
| −3 | capability blast radius (moderate) — 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.
Findings 1
medium Unconstrained URL/host parameter "host" on "email_configure"MTC-CAP-007
Tool "email_configure" takes a URL/host parameter "host" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool email_configure · inputSchema.properties.host
Tools 16
Each tool and what it can reach — statically extracted from the published source.
email_configurenetwork egressemail_apply_rulesno sensitive capabilityemail_create_folderno sensitive capabilityemail_deleteno sensitive capabilityemail_forwardno sensitive capabilityemail_get_attachmentno sensitive capabilityemail_get_messageno sensitive capabilityemail_list_foldersno sensitive capabilityemail_list_messagesno sensitive capabilityemail_markno sensitive capability
Show 6 more tools ↓
email_move_messagesno sensitive capabilityemail_replyno sensitive capabilityemail_save_draftno sensitive capabilityemail_sendno sensitive capabilityemail_send_draftno sensitive capabilityemail_test_connectionno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (16 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>".
Versions 2
Scan 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 |
|---|---|---|---|---|
v0.5.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-08-25 |
v0.4.0 |
A 98/100 | 1 | 1.5.0 | 2026-07-22 |
Embed this score
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.
Verify this score yourself
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 --online --registry pypiOther implementations of Email 19
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、企业邮箱等多种邮箱服务商的自动配置和邮件发送功能
More in Web, Search & Scraping
Agent IP: MCP server with patents search tools
MCP server for searching the Agent Almanac — the public catalog of 9,000+ Model Context Protocol servers. Find, install, and discover MCP servers from inside Claude Desktop, Cursor, Continue, Zed, or any MCP-aware agent.
Search agents & MCP servers by capability, with daily-observed pricing, liveness and market data.
Verified merchants accepting agentic payments on Lightning/L402/BOLT12/USDT — search, verify, pay.
Airframe MCP Client - Connect agents to Airframe's product intelligence
Amazon product search demand over time, with growth for any keyword. Free key at trendsmcp.ai