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/ishaan-skyacres/gmail-multi-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/ishaan-skyacres/gmail-multi-mcp/gmail-multi-mcp)<a href="https://agentmods.dev/mcp/ishaan-skyacres/gmail-multi-mcp/gmail-multi-mcp"><img src="https://agentmods.dev/badge/mcp/ishaan-skyacres/gmail-multi-mcp/gmail-multi-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/ishaan-skyacres/gmail-multi-mcp/gmail-multi-mcp"><img src="https://agentmods.dev/badge/mcp/ishaan-skyacres/gmail-multi-mcp/gmail-multi-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
gmail-multi-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 8d 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 gmail-multi-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
{ "gmail-multi-mcp": { "command": "npx", "args": [ "-y", "gmail-multi-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.
- 8d ago First seen · 9 lines scan A 6907d1053bd6
gmail-multi-mcp is an MCP server published in the GitHub repository ishaan-skyacres/gmail-multi-mcp (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 gmail-multi-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
mailwarden
Native Gmail MCP server: search, labels, archive, trash, attachments, and snooze. Runs locally from the mailwarden npm package. Needs 4 environment variables to run.
multi-account-gmail-mcp
MCP server "multi-account-gmail-mcp" as configured in zack-bolich/multi-account-gmail-mcp. Runs locally from the multi-account-gmail-mcp npm package.
gmail-mcp
Gmail MCP server for reading Gmail messages via Model Context Protocol. Runs locally from the @symbolstar/gmail-mcp npm package.
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.
multi-account-gmail-mcp
Multi-account Gmail MCP server for AI agents. Runs locally from the multi-account-gmail-mcp Python package. Needs 3 environment variables to run.
outlook_multi_mailbox
MCP server "outlookmultimailbox" as configured in ftaricano/mcp-outlook. Runs ${CODEX_PLUGIN_ROOT}/dist/plugin/stdio.js with node.