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/Metaverse-Cloud/engagelab-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/metaverse-cloud/engagelab-email-mcp/engagelab-email)<a href="https://agentmods.dev/mcp/metaverse-cloud/engagelab-email-mcp/engagelab-email"><img src="https://agentmods.dev/badge/mcp/metaverse-cloud/engagelab-email-mcp/engagelab-email/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/metaverse-cloud/engagelab-email-mcp/engagelab-email"><img src="https://agentmods.dev/badge/mcp/metaverse-cloud/engagelab-email-mcp/engagelab-email.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
engagelab-email 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.
What it actually says
{
"engagelab-email": {
"command": "npx",
"args": [
"-y",
"@engagelabemail/mcp"
],
"env": {
"ENGAGELAB_EMAIL_SECRET_KEY": "",
"ENGAGELAB_EMAIL_BASE_URL": ""
}
}
}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 · 13 lines scan A 36088d973816
engagelab-email is an MCP server published in the GitHub repository Metaverse-Cloud/engagelab-email-mcp (0 stars, last pushed 11d 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-09-04.
Other mcp servers, from other repositories
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP. Runs locally from the obsidian-mcp-server npm package. Needs 10 environment variables to run.
google-workspace
Give AI agents access to Gmail, Calendar, Drive, and more — multi-account, manifest-driven. Runs locally from the @aaronsb/google-workspace-mcp npm package. Needs 2 environment variables to run.
mcp-telegram
MCP server for Telegram userbot — messages, media, reactions, polls & more. Built on GramJS/MTProto. Runs locally from the @overpod/mcp-telegram npm package. Needs 2 environment variables to run.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
a2cr-mcp
Local MCP workspace for AI agent handoff checkpoints, WorkStash notes, and WorkThreads. Runs locally from the a2cr-mcp Python package. Needs 1 environment variable to run.
n8n-manager-mcp
MCP server for n8n workflow management -- view, create, sync and manage workflows via AI. Runs locally from the n8n-manager-mcp npm package.