pulsemcp verified Safe content atomic mcp-remote

Proton Drive

This MCP server provides file system access to Proton Drive through cross-platform path detection and standard file operations, enabling AI assistants to read, write, create, and manage files within the encrypted cloud storage service. Built by anyrxo using TypeScript with the Model Context Protocol SDK, it automatically detects Proton Drive installation paths across macOS, Windows, and Linux systems, offers seven core tools including directory listing, file reading/writing, folder creation, and file deletion with security validation to prevent path traversal attacks. The implementation features platform-specific mount point detection with fallback locations, relative path handling for intuitive navigation, comprehensive file metadata retrieval with formatted size display, and robust error handling with proper MCP error codes, making it valuable for users who want AI-assisted file management within their Proton Drive storage, automated document organization workflows, and secure cloud-based file operations without manual Proton Drive interface navigation.

Cognium trust score

100%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: security
Source: PulseMCP
Repository: github.com/anyrxo/proton-drive-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Proton Drive from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"