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/Br0ski777/email-send-x402Wrote 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/br0ski777/email-send-x402/email-send)<a href="https://agentmods.dev/mcp/br0ski777/email-send-x402/email-send"><img src="https://agentmods.dev/badge/mcp/br0ski777/email-send-x402/email-send/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/br0ski777/email-send-x402/email-send"><img src="https://agentmods.dev/badge/mcp/br0ski777/email-send-x402/email-send.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
email-send 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
{
"email-send": {
"url": "https://email-send.api.klymax402.com/mcp",
"type": "sse"
}
}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 · 6 lines scan A c9fa986a85f9
email-send is an MCP server published in the GitHub repository Br0ski777/email-send-x402 (0 stars, last pushed 7d 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
email-verification
Verify emails: syntax, MX records, disposable detection, quality score 0-100. x402 USDC. Remote server at email-verification.api.klymax402.com.
email-finder
Find email addresses from name and company domain. x402 paid. Remote server at email-finder.api.klymax402.com.
blockrun-mcp
Live data for AI agents: search, research, markets, crypto, X/Twitter. Pay per call. Runs locally from the @blockrun/mcp npm package. Needs 1 environment variable to run.
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.
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.
x402-list-mcp
MCP server for x402-list: discover x402 payment services, on-chain-verified facilitator settlement volume, server-ranked recommendations, and paid on-demand assessments (x402 pass-through, never holds keys). Thin wrapper over the public x402-list API. Runs locally from the x402-list-mcp npm package. Needs 2…