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/plugins/shipmail-to/shipmail-mcp/shipmail)<a href="https://agentmods.dev/plugins/shipmail-to/shipmail-mcp/shipmail"><img src="https://agentmods.dev/badge/plugins/shipmail-to/shipmail-mcp/shipmail/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/plugins/shipmail-to/shipmail-mcp/shipmail"><img src="https://agentmods.dev/badge/plugins/shipmail-to/shipmail-mcp/shipmail.svg" alt="Reviewed on agentmods" width="80" 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 yesterday.
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
{
"displayName": "Shipmail",
"name": "shipmail",
"version": "0.9.6",
"description": "Modern email for your business. Inboxes, calendars, newsletters, bookings and an AI assistant, plus transactional email and an API for your agents. Everything on your own domain, in one subscription.",
"author": {
"name": "Shipmail",
"email": "[email protected]",
"url": "https://shipmail.to"
},
"homepage": "https://shipmail.to/docs/mcp",
"privacyPolicyUrl": "https://shipmail.to/privacy",
"supportUrl": "https://shipmail.to/support",
"documentationUrl": "https://shipmail.to/docs/mcp",
"termsOfServiceUrl": "https://shipmail.to/terms",
"icon": "./assets/shipmail-mark.svg",
"repository": "https://github.com/shipmail-to/shipmail-mcp",
"license": "MIT",
"keywords": [
"email",
"business-email",
"custom-domain",
"agent-inbox",
"calendar",
"mcp"
],
"skills": "./skills/",
"mcpServers": "./.mcp.json"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 108 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- yesterday Changed b7f257c45e83
- 5d ago Changed cf14ba2cc568
- 8d ago Changed 4df61a9b51fe
- 9d ago Changed 2d982370afb4
- 13d ago Changed 14a1a427c9cb
- 19d ago Changed edfd5e937d5a
- 20d ago First seen · 30 lines scan A 9d27687079ab
shipmail is a plugin published in the GitHub repository shipmail-to/shipmail-mcp (1 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-26.
Other plugins, from other repositories
email-mcp
Multi-service email platform for MCP-compatible clients.
better-email-mcp
Email management via IMAP/SMTP — multi-account.
mcp-email-server
Email MCP tools with safe, non-secret setup and diagnostic guidance.
e2a
Open-source email API for applications and AI agents — transactional sending from any product, per-agent two-way inboxes, structured SPF/DKIM/DMARC evidence, and a queryable event log. 80 MCP tools over hosted streamable HTTP with OAuth.
openclaw
OpenClaw AI assistant integration. Chat, manage sessions, access memory, and run async tasks through your OpenClaw instance.
raindrop-mcp
Raindrop.io MCP Server.