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/laschopin/better-email-mcp-workerWrote 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/laschopin/better-email-mcp-worker/better-email-mcp)<a href="https://agentmods.dev/mcp/laschopin/better-email-mcp-worker/better-email-mcp"><img src="https://agentmods.dev/badge/mcp/laschopin/better-email-mcp-worker/better-email-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/laschopin/better-email-mcp-worker/better-email-mcp"><img src="https://agentmods.dev/badge/mcp/laschopin/better-email-mcp-worker/better-email-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
better-email-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 10d 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 better-email-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
{
"better-email-mcp": {
"command": "npx",
"args": [
"-y",
"@n24q02m/better-email-mcp"
],
"env": {
"EMAIL_CREDENTIALS": ""
}
}
}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.
- 10d ago First seen · 12 lines scan A 40b963a70109
better-email-mcp is an MCP server published in the GitHub repository laschopin/better-email-mcp-worker (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 better-email-mcp, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
taskview
MCP (Model Context Protocol) server for TaskView — lets AI assistants (Claude Code, Claude Desktop, etc.) manage projects and tasks via the TaskView API. Runs locally from the taskview-mcp npm package. Needs 2 environment variables to run.
multisim-mcp
Unofficial MCP server for NI Multisim Automation API. Runs locally from the multisim-mcp Python package. Needs 1 environment variable to run.
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.
whatsapp-mcp
Python MCP server for whatsapp-mcp. Consumes the Go bridge REST API and exposes tools to Claude. Runs locally from the adelaidasofia-whatsapp-mcp Python package. Needs 9 environment variables to run.
render-useful-mcp
MCP server for the Render Public API: all 207 endpoints plus workflow tools. Runs locally from the render-useful-mcp npm package. Needs 5 environment variables to run.
mcp-ecc
MCP server for Email, Calendar & Contacts — Google, Microsoft 365, Zoho, IMAP/SMTP, CalDAV, CardDAV. Runs locally from the mcp-ecc npm package. Needs 1 environment variable to run.