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/Sendmux/sendmux-sdkWrote 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/sendmux/sendmux-sdk/mcp-sendmux-mcp)<a href="https://agentmods.dev/mcp/sendmux/sendmux-sdk/mcp-sendmux-mcp"><img src="https://agentmods.dev/badge/mcp/sendmux/sendmux-sdk/mcp-sendmux-mcp/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/sendmux/sendmux-sdk/mcp-sendmux-mcp"><img src="https://agentmods.dev/badge/mcp/sendmux/sendmux-sdk/mcp-sendmux-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sendmux-mcp 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 1mo 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
{
"sendmux-mcp": {
"command": "uvx",
"args": [
"sendmux-mcp"
],
"env": {
"SENDMUX_MCP_SURFACES": "mailbox,management,sending",
"SENDMUX_MAILBOX_API_KEY": "",
"SENDMUX_MANAGEMENT_API_KEY": "",
"SENDMUX_SENDING_API_KEY": ""
}
}
}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.
- 1mo ago First seen · 14 lines scan A d15c4d80efaa
sendmux-mcp is an MCP server published in the GitHub repository Sendmux/sendmux-sdk (62 stars, last pushed yesterday), 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-30.
Other mcp servers, from other repositories
fluxmail
Read, search, draft, send, and organize email through Gmail, Outlook, and IMAP/SMTP mailboxes. Runs locally from the fluxmail npm package. Needs 4 environment variables to run.
fluxmail
Self-hosted email API with MCP and REST support for Gmail, Outlook, and IMAP/SMTP. Runs locally from the fluxmail npm package.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
thunderbird-cli
Give AI agents full read/write email access via Mozilla Thunderbird. Zero credentials. Runs locally from the thunderbird-cli-mcp npm package. Needs 2 environment variables to run.
x-openapi-flow-mcp
OpenAPI lifecycle guard and MCP sidecar for policy-driven API orchestration. Runs locally from the x-openapi-flow npm package.
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.