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.
git clone --depth 1 https://github.com/samihalawa/email-smtp-imap-mcpWrote 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/samihalawa/email-smtp-imap-mcp/email-smtp-imap-email-smtp-imap)<a href="https://agentmods.dev/mcp/samihalawa/email-smtp-imap-mcp/email-smtp-imap-email-smtp-imap"><img src="https://agentmods.dev/badge/mcp/samihalawa/email-smtp-imap-mcp/email-smtp-imap-email-smtp-imap/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/samihalawa/email-smtp-imap-mcp/email-smtp-imap-email-smtp-imap"><img src="https://agentmods.dev/badge/mcp/samihalawa/email-smtp-imap-mcp/email-smtp-imap-email-smtp-imap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
email-smtp-imap 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 yesterday.
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-smtp-imap": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"EMAIL_ACCOUNTS_JSON": "${user_config.email_accounts_json}",
"DEFAULT_EMAIL_ACCOUNT": "${user_config.default_email_account}"
}
}
}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.
- yesterday First seen · 13 lines scan A ac1e8b2299a1
email-smtp-imap is an MCP server published in the GitHub repository samihalawa/email-smtp-imap-mcp (25 stars, last pushed yesterday), licensed MIT. 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-11-01.
Other mcp servers, from other repositories
imap-mcp-server
IMAP/SMTP MCP server to search, read, organize, send, reply & forward email for AI assistants. Runs locally from the imap-mcp-server npm package.
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 — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage. Runs locally from the @codefuturist/email-mcp npm package.
pylos-mcp
Email MCP server for Gmail, Outlook and any IMAP mailbox, hardened against prompt injection. Runs locally from the pylos-mcp npm package. Needs 8 environment variables to run.
mailbox-mcp
Multi-account email MCP server for Gmail, IMAP, and JMAP: search, send, drafts, labels. Runs locally from the mailbox-mcp npm package. Needs 1 environment variable to run.
emails
Never-stored live email: read, send and triage Gmail, Outlook / Microsoft 365, or any IMAP mailbox. Runs locally from the mcpemails npm package. Needs 1 environment variable to run.