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/shipmail-to/shipmail-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/shipmail-to/shipmail-mcp/shipmail)<a href="https://agentmods.dev/mcp/shipmail-to/shipmail-mcp/shipmail"><img src="https://agentmods.dev/badge/mcp/shipmail-to/shipmail-mcp/shipmail.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
shipmail 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
{
"shipmail": {
"type": "http",
"url": "https://shipmail.to/api/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.
- 8d ago First seen · 6 lines scan A 4d4b4ae6e081
shipmail is an MCP server published in the GitHub repository shipmail-to/shipmail-mcp (1 stars, last pushed 6d 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
inbound-email
Turn inbound email into a webhook — verify, parse, route, and store incoming messages. Remote server at mcp.mailkite.dev.
mailkite
Send email, manage domains, DNS, webhooks, templates, and inbound routing on MailKite. Runs locally from the @mailkite/mcp npm package. Needs 1 environment variable to run.
agent-mail
Give an AI agent its own inbox — receive email as a webhook, send over a verified domain. Remote server at mcp.mailkite.dev.
email-agent
Email for AI agents — send, receive as a webhook, manage domains, templates, routing. Remote server at mcp.mailkite.dev.
mail-receive
Receive inbound email as clean JSON — manage domains, routes, and webhooks. MailKite. Remote server at mcp.mailkite.dev.
mail-send
Send transactional email over a verified domain — templates, attachments, custom headers. Remote server at mcp.mailkite.dev.