Proton Drive MCP Server

proton-drive-mcp npm v1.0.35

Published by googlarz — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server and CLI that gives Claude full access to Proton Drive — upload, download, share, and manage your end-to-end encrypted files without leaving the conversation.

Trust grade
B
87/100
Last scanned get badge →
Trust
B · 87/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 94 − adoption risk = 87/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Description names a credential store the tool cannot reach MTC-INJ-SCHEMA-1 injection

2. Client adoption risk — 94 − 7 = 87. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 6

high Shell/command execution in server code (dist/utils/subprocess.js)MTC-SRC-002

In the server's implementation (`dist/utils/subprocess.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from "node:child_process"; import { promisify } from "node:util"; import { DriveCliError, DriveCliNotFoundE

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/subprocess.js

medium Description names a credential store the tool cannot reachMTC-INJ-SCHEMA-1

Tool "drive_auth_logout" describes a credential store (SSH keys, cloud credentials, a keychain or an equivalent) that nothing in its input schema can address. A tool's interface is the honest statement of what it touches; prose that reaches past it is addressed to the model, not to a reader.

Evidence: keychain

Fix: Remove the reference, or expose the target as an explicit, validated parameter so the client can see and consent to what the tool reads.

Location: tool drive_auth_logout · description

medium Tool "drive_write_file" can modify the filesystemMTC-CAP-002

Tool "drive_write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool drive_write_file

low Mutating tool "drive_write_file" declares no destructiveHintMTC-CAP-005

Tool "drive_write_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool drive_write_file

low Unconstrained path parameter "path" on "drive_read_file"MTC-CAP-008

Tool "drive_read_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool drive_read_file · inputSchema.properties.path

low Unconstrained path parameter "path" on "drive_write_file"MTC-CAP-008

Tool "drive_write_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool drive_write_file · inputSchema.properties.path

Tools 38

Each tool and what it can reach — statically extracted from the published source.

  • drive_downloadingests untrusted input
  • drive_read_filereads sensitive data
  • drive_write_filewrites files
  • photos_downloadingests untrusted input
  • drive_auth_logoutno sensitive capability
  • drive_auth_statusno sensitive capability
  • drive_copyno sensitive capability
  • drive_deleteno sensitive capability
  • drive_empty_trashno sensitive capability
  • drive_infono sensitive capability
Show 28 more tools ↓
  • drive_invitation_acceptno sensitive capability
  • drive_invitation_rejectno sensitive capability
  • drive_listno sensitive capability
  • drive_list_invitationsno sensitive capability
  • drive_list_trashno sensitive capability
  • drive_mkdirno sensitive capability
  • drive_moveno sensitive capability
  • drive_renameno sensitive capability
  • drive_restoreno sensitive capability
  • drive_share_inviteno sensitive capability
  • drive_share_leaveno sensitive capability
  • drive_share_remove_allno sensitive capability
  • drive_share_remove_urlno sensitive capability
  • drive_share_revokeno sensitive capability
  • drive_share_set_urlno sensitive capability
  • drive_share_statusno sensitive capability
  • drive_trashno sensitive capability
  • drive_uploadno sensitive capability
  • drive_versionno sensitive capability
  • photos_add_to_albumno sensitive capability
  • photos_create_albumno sensitive capability
  • photos_delete_albumno sensitive capability
  • photos_list_album_photosno sensitive capability
  • photos_list_albumsno sensitive capability
  • photos_list_timelineno sensitive capability
  • photos_remove_from_albumno sensitive capability
  • photos_update_albumno sensitive capability
  • photos_uploadno sensitive capability

What this scan could not see

Versions 8

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.35 latest B 87/100 6 1.13.0 2026-09-07
v1.0.32 B 87/100 6 1.13.0 2026-09-01
v1.0.29 B 87/100 6 1.12.1 2026-08-21
v1.0.28 B 87/100 6 1.12.1 2026-08-13
v1.0.27 B 87/100 6 1.12.1 2026-08-12
Show 3 more versions ↓
v1.0.26 B 87/100 6 1.12.1 2026-08-10
v1.0.25 B 87/100 6 1.12.1 2026-08-05
v1.0.23 B 87/100 6 1.12.1 2026-08-04

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 87/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/proton-drive-mcp/badge.svg)](https://mcptrustchecker.com/registry/proton-drive-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/proton-drive-mcp"><img src="https://mcptrustchecker.com/registry/proton-drive-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/proton-drive-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan proton-drive-mcp --online

Use the free API → How scoring works

More in Productivity & Workflow