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/mailkite/mailkite-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/mailkite/mailkite-mcp/mail-receive)<a href="https://agentmods.dev/mcp/mailkite/mailkite-mcp/mail-receive"><img src="https://agentmods.dev/badge/mcp/mailkite/mailkite-mcp/mail-receive/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/mailkite/mailkite-mcp/mail-receive"><img src="https://agentmods.dev/badge/mcp/mailkite/mailkite-mcp/mail-receive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mail-receive 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What else server.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 6 lines scan A f1e5d81bf762
mail-receive is an MCP server published in the GitHub repository mailkite/mailkite-mcp (0 stars, last pushed 9d ago), with no licence file. 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
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.
send16-mcp
Email for AI agents: send mail, manage contacts, automations & webhooks. Zero-DNS first send. Runs locally from the send16-mcp npm package. Needs 1 environment variable to run.
mcp-server
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified. Remote server at api.e2a.dev.
shipmail
MCP server "shipmail", hosted remotely at shipmail.to, as configured in shipmail-to/shipmail-mcp.
email-verification
Verify emails: syntax, MX records, disposable detection, quality score 0-100. x402 USDC. Remote server at email-verification.api.klymax402.com.
dead-simple-email
Dead Simple Email — Python SDK for the email API for AI agents. Runs locally from the deadsimple-email Python package. Needs 1 environment variable to run.