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/96b2gwbdg8-dev/imap_mail_connectorWrote 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/96b2gwbdg8-dev/imap_mail_connector/imap-mail-mcp)<a href="https://agentmods.dev/mcp/96b2gwbdg8-dev/imap_mail_connector/imap-mail-mcp"><img src="https://agentmods.dev/badge/mcp/96b2gwbdg8-dev/imap_mail_connector/imap-mail-mcp/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/96b2gwbdg8-dev/imap_mail_connector/imap-mail-mcp"><img src="https://agentmods.dev/badge/mcp/96b2gwbdg8-dev/imap_mail_connector/imap-mail-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
imap-mail-mcp 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 9d 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.
This is a copy
100% identical to imap-mail-mcp — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "imap-mail-mcp": { "command": "npx", "args": [ "-y", "imap-mail-mcp" ] } }
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.
- 9d ago First seen · 9 lines scan A 18fbf92c5639
imap-mail-mcp is an MCP server published in the GitHub repository 96b2gwbdg8-dev/imap_mail_connector (0 stars, last pushed 1mo 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. It is 100% identical to imap-mail-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
proton-bridge-mcp
MCP server "proton-bridge-mcp" as configured in Considus/proton-bridge-mcp. Launched with https://github.com/Considus/proton-bridge-mcp/releases/download/v1.2.2/proton-br.
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.
readndraft
MCP server "readndraft" as configured in LeoPhoenixT/readNdraft-imap-mcp. Launched with uv tool run [email protected] mcp.
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.
proton-mail-mcp
Unofficial MCP server for Proton Mail (not affiliated with Proton AG) — send, read, search, and organize email over SMTP and IMAP. Runs locally from the proton-mail-mcp npm package.
imap-mcp
MCP server "imap-mcp" as configured in LeeFlannery/imap-mcp. Runs locally from the imap-mcp Python package.