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/borealstack/proton-drive-cli-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/borealstack/proton-drive-cli-mcp/proton-drive-cli-mcp-proton-drive-cli)<a href="https://agentmods.dev/mcp/borealstack/proton-drive-cli-mcp/proton-drive-cli-mcp-proton-drive-cli"><img src="https://agentmods.dev/badge/mcp/borealstack/proton-drive-cli-mcp/proton-drive-cli-mcp-proton-drive-cli.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
proton-drive-cli 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 6d 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
{
"proton-drive-cli": {
"command": "npx",
"args": [
"-y",
"@borealstack/proton-drive-cli-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.
- 6d ago First seen · 9 lines scan A ffbc6b051968
proton-drive-cli is an MCP server published in the GitHub repository borealstack/proton-drive-cli-mcp (0 stars, last pushed 2mo 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
multi-gmail-mcp
Manage multiple Gmail accounts in Claude Desktop — search, send, reply, draft, and organize. Runs locally from the multi-gmail-mcp npm package. Needs 2 environment variables to run.
mcp-clipboard
MCP server that reads and writes the system clipboard — tables, text, code, JSON, URLs, images, and more. Runs locally from the mcp-clipboard Python package.
google-workspace-mcp
MCP server for Google Workspace: Docs, Sheets, Drive, Gmail, Calendar, Slides, and Forms. Runs locally from the google-workspace-mcp npm package.
tg-mcp
Local MCP server for your Telegram personal account — channels, digests, messaging, folders and more. Runs locally from the tg-mcp npm package.
kafka-schema-registry
MCP server "kafka-schema-registry" as configured in aywengo/kafka-schema-reg-mcp. Runs kafka_schema_registry_unified_mcp.py with python. Needs 3 environment variables to run.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.