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/tokencanopy/e2aWrote 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/tokencanopy/e2a/e2a-e2a)<a href="https://agentmods.dev/mcp/tokencanopy/e2a/e2a-e2a"><img src="https://agentmods.dev/badge/mcp/tokencanopy/e2a/e2a-e2a/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/tokencanopy/e2a/e2a-e2a"><img src="https://agentmods.dev/badge/mcp/tokencanopy/e2a/e2a-e2a.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
e2a 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 1mo 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
{
"e2a": {
"type": "http",
"url": "https://api.e2a.dev/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.
- 1mo ago First seen · 6 lines scan A 319cf38b08cb
e2a is an MCP server published in the GitHub repository tokencanopy/e2a (194 stars, last pushed 6d ago), licensed Apache-2.0. 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-30.
Other mcp servers, from other repositories
mcp
Official MCP Server for Mailtrap. Runs locally from the mcp-mailtrap npm package. Needs 2 environment variables to run.
proton-safe
Client-agnostic Proton Mail MCP server with safe reads, bounded attachment text extraction, and explicitly confirmed drafts. Runs locally from the proton-safe-mcp Python package.
proton-safe-mcp
Client-agnostic Proton Mail MCP server with safe reads, bounded attachment text extraction, and explicitly confirmed drafts. Runs locally from the proton-safe-mcp Python package. Needs 2 environment variables to run.
shipmail-mcp
Shipmail MCP server for AI agent custom-domain email inboxes with REST API and webhooks. Runs locally from the shipmail-mcp npm package. Needs 1 environment variable to run.
shipmail
MCP server "shipmail", hosted remotely at shipmail.to, as configured in shipmail-to/shipmail-mcp.
baryon-mcp
MCP server "baryon-mcp" as configured in combor/baryon-mcp. Launched with https://github.com/combor/baryon-mcp/releases/download/v0.6.2/baryon-mcp-darwin-.