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/dazzle-blip/code-protonboundWrote 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/dazzle-blip/code-protonbound/protonbound)<a href="https://agentmods.dev/mcp/dazzle-blip/code-protonbound/protonbound"><img src="https://agentmods.dev/badge/mcp/dazzle-blip/code-protonbound/protonbound/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/dazzle-blip/code-protonbound/protonbound"><img src="https://agentmods.dev/badge/mcp/dazzle-blip/code-protonbound/protonbound.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
protonbound 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.
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 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 · 8 lines scan A 80c105ad951b
protonbound is an MCP server published in the GitHub repository dazzle-blip/code-protonbound (2 stars, last pushed yesterday), 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
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.
proton-mail-mcp
Unofficial Proton Mail MCP — send, read, search & organize email over SMTP and IMAP. Runs locally from the proton-mail-mcp npm package. Needs 15 environment variables to run.
email-mcp
IMAP/SMTP email MCP server — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage. Runs locally from the @codefuturist/email-mcp npm package.
pylos-mcp
Read-focused, prompt-injection-hardened email MCP server for any IMAP provider. Runs locally from the pylos-mcp npm package. Needs 5 environment variables to run.
mcp-one
Model Context Protocol (MCP) server for one.com mailboxes. Full email management (IMAP/SMTP) for Claude and AI agents. Runs locally from the @xtnd-dynamics/mcp-one npm package.
mcp-server-imap
Email tools for any IMAP/SMTP provider: list, read, search, send, and manage messages. Runs locally from the @aiwerk/mcp-server-imap npm package. Needs 6 environment variables to run.