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-finder-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-finder-x402/email-finder)<a href="https://agentmods.dev/mcp/br0ski777/email-finder-x402/email-finder"><img src="https://agentmods.dev/badge/mcp/br0ski777/email-finder-x402/email-finder/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-finder-x402/email-finder"><img src="https://agentmods.dev/badge/mcp/br0ski777/email-finder-x402/email-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
email-finder 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 11d 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-finder": {
"url": "https://email-finder.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.
- 11d ago First seen · 6 lines scan A 808d5f610ba6
email-finder is an MCP server published in the GitHub repository Br0ski777/email-finder-x402 (0 stars, last pushed 9d 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.
phone-validation
Validate phone numbers worldwide: carrier, line type, country, E.164. x402. Remote server at phone-validation.api.klymax402.com.
email-send
Send emails programmatically via Resend. Text and HTML. x402 micropayment. Remote server at email-send.api.klymax402.com.
sms-validator
Validate SMS-capable phone numbers — mobile vs landline, E.164 format. x402 micropayment. Remote server at sms-validator.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.