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/boutquin/mcp-server-emailWrote 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/boutquin/mcp-server-email/email)<a href="https://agentmods.dev/mcp/boutquin/mcp-server-email/email"><img src="https://agentmods.dev/badge/mcp/boutquin/mcp-server-email/email/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/boutquin/mcp-server-email/email"><img src="https://agentmods.dev/badge/mcp/boutquin/mcp-server-email/email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
email 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 1mo 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": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/boutquin/mcp-server-email:latest"
],
"env": {
"EMAIL_CONFIG_FILE": "",
"EMAIL_ACCOUNTS": ""
}
}
}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.
- 1mo ago First seen · 15 lines scan A 04805b7a8b33
email is an MCP server published in the GitHub repository boutquin/mcp-server-email (3 stars, last pushed 7mo ago), 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-08-31.
Other mcp servers, from other repositories
baryon-mcp
MCP server "baryon-mcp" as configured in combor/baryon-mcp. Launched with https://github.com/combor/baryon-mcp/releases/download/v0.6.2/baryon-mcp-darwin-.
email-dev
MCP server "email-dev" as configured in Wh1isper/mcp-email-server. Launched with {{ PWD }}/.venv/bin/python {{ PWD }}/mcp_email_server/cli.py stdio.
graymatter
MCP server "graymatter" as configured in angelnicolasc/graymatter. Launched with graymatter mcp serve.
mcp
Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox. Runs locally from the @agenticmail/mcp npm package. Needs 3 environment variables to run.
mcp-server
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified. Remote server at api.e2a.dev.
e2a
MCP server "e2a", hosted remotely at api.e2a.dev, as configured in tokencanopy/e2a.