Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/wh1isper/mcp-email-server/email-devgit clone --depth 1 https://github.com/Wh1isper/mcp-email-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/wh1isper/mcp-email-server/email-dev)<a href="https://agentmods.dev/mcp/wh1isper/mcp-email-server/email-dev"><img src="https://agentmods.dev/badge/mcp/wh1isper/mcp-email-server/email-dev.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
email-dev scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"email-dev": {
"command": "{{ PWD }}/.venv/bin/python {{ PWD }}/mcp_email_server/cli.py",
"args": [
"stdio"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 8 lines scan A ac0bb04eb45e
email-dev is an MCP server published in the GitHub repository Wh1isper/mcp-email-server (321 stars, last pushed yesterday), licensed BSD-3-Clause. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
better-email-mcp
IMAP/SMTP MCP server for Email with composite tools. Multi-account, auto-discovery. Runs locally from the @n24q02m/better-email-mcp npm package. Needs 1 environment variable to run.
proton-mail-mcp
Unofficial Proton Mail MCP — send, read, search & organize email over SMTP and IMAP. Runs locally from the proton-mail-mcp npm package. Needs 15 environment variables to run.
email-mcp
IMAP/SMTP email MCP server — 47 tools, IMAP IDLE push, multi-account, AI triage. Runs locally from the @codefuturist/email-mcp npm package.
proton-safe
Client-agnostic, draft-only Proton Mail MCP server with secure attachment staging. Runs locally from the proton-safe-mcp Python package.
proton-safe-mcp
Client-agnostic, draft-only Proton Mail MCP server with secure attachment staging. Runs locally from the proton-safe-mcp Python package. Needs 2 environment variables to run.
mcp-server-imap
Email tools for any IMAP/SMTP provider: list, read, search, send, and manage messages. Runs locally from the @aiwerk/mcp-server-imap npm package. Needs 6 environment variables to run.