@iflow-mcp/email-mcp
npm
v1.0.0
Published by @iflow-mcp — 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.
通用邮箱MCP服务器 - 支持QQ、163、Gmail(由于谷歌政策不支持OAuth2.0,所以无法使用)、Outlook、企业邮箱等多种邮箱服务商的自动配置和邮件发送功能
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.
Each tool and what it can reach — statically extracted from the published source.
send_emailnetwork egressconfigure_email_serverno sensitive capabilityget_email_contentno sensitive capabilityget_recent_emailsno sensitive capabilitylist_supported_providersno sensitive capabilitysetup_email_accountno sensitive capabilitytest_email_connectionno 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.0.0 latest |
A 96/100 | 0 | 1.13.0 | 2026-09-07 |
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 @iflow-mcp/email-mcp --online
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 server for agent email that creates voidmail.ai inboxes and can send, receive, search, and manage aliases with an API key.
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