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/elie222/inbox-zeroWrote 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/elie222/inbox-zero/inbox-zero)<a href="https://agentmods.dev/mcp/elie222/inbox-zero/inbox-zero"><img src="https://agentmods.dev/badge/mcp/elie222/inbox-zero/inbox-zero/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/elie222/inbox-zero/inbox-zero"><img src="https://agentmods.dev/badge/mcp/elie222/inbox-zero/inbox-zero.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
inbox-zero 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 today.
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- today First seen · 6 lines scan A e8e579842922
inbox-zero is an MCP server published in the GitHub repository elie222/inbox-zero (12,809 stars, last pushed yesterday), with no licence file. 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-10-26.
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.
apple-mail-mcp
Fast local MCP server for Apple Mail: search, read, triage, verified send. Works with Claude, Cursor, VS Code, or any MCP client. Runs locally from the apple-mailbox-mcp Python package.
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
Read-focused, prompt-injection-hardened email MCP server for any IMAP provider. Runs locally from the pylos-mcp npm package. Needs 5 environment variables to run.
dead-simple-email
Dead Simple Email — Python SDK for the email API for AI agents. Runs locally from the deadsimple-email Python package. Needs 1 environment variable to run.
mcp-one
Model Context Protocol (MCP) server for one.com mailboxes. Full email management (IMAP/SMTP) for Claude and AI agents. Runs locally from the @xtnd-dynamics/mcp-one npm package.