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/ciphersolutions-dev/private-email-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/ciphersolutions-dev/private-email-mcp/privateemail-mcp)<a href="https://agentmods.dev/mcp/ciphersolutions-dev/private-email-mcp/privateemail-mcp"><img src="https://agentmods.dev/badge/mcp/ciphersolutions-dev/private-email-mcp/privateemail-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
privateemail-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 7d 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
{ "privateemail-mcp": { "command": "uvx", "args": [ "privateemail-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.
- 7d ago First seen · 8 lines scan A 7d09de5466d3
privateemail-mcp is an MCP server published in the GitHub repository ciphersolutions-dev/private-email-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. 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
better-email-mcp
IMAP/SMTP MCP server for Email with composite tools. Multi-account, auto-discovery. Runs locally from the @n24q02m/better-email-mcp npm package. Needs 1 environment variable to run.
email-mcp-server
A MCP Server + CLI Tool that perform email operations. Runs locally from the @0xshariq/email-mcp-server npm package.
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.
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.
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.
mcp
Unlimited agent mailboxes — create identities, read/wait for mail, extract OTPs, send email. Runs locally from the @openagentemail/mcp npm package. Needs 2 environment variables to run.