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/wildsurfer/your-mail-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/wildsurfer/your-mail-mcp/your-mail)<a href="https://agentmods.dev/mcp/wildsurfer/your-mail-mcp/your-mail"><img src="https://agentmods.dev/badge/mcp/wildsurfer/your-mail-mcp/your-mail/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/wildsurfer/your-mail-mcp/your-mail"><img src="https://agentmods.dev/badge/mcp/wildsurfer/your-mail-mcp/your-mail.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
your-mail 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.
What it actually says
{
"your-mail": {
"command": "docker",
"args": [
"exec",
"-i",
"your-mail-mcp",
"your-mail-mcp",
"stdio"
]
}
}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 · 12 lines scan A ef9dcfbc3cb6
your-mail is an MCP server published in the GitHub repository wildsurfer/your-mail-mcp (12 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-08-31.
Other mcp servers, from other repositories
email-mcp
Provider-neutral email MCP server over Streamable HTTP. Runs locally from the @xingyuchen/email-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.
mail-index
Local-first, read-only MCP server for recall over your Gmail: search, contacts, threads, digests. Runs locally from the mail-index npm package.
mail-muncher
MCP server "mail-muncher" as configured in craigjmidwinter/mail-muncher. Launched with mail-muncher mcp.
mail-agent-mcp
MCP server "mail-agent-mcp" as configured in SinoEdwards/mail-agent-mcp. Runs locally from the mail-agent-mcp npm package.
gmail-postmaster-tools
MCP server "gmail-postmaster-tools" as configured in optipub/gmail-postmaster-tools-mcp. Launched with https://github.com/optipub/gmail-postmaster-tools-mcp/releases/download/v1.0.1/g.