# Proton Mail (pypi · proton-mcp)

Read, search and send Proton Mail through Proton Mail Bridge, with sending kept on approval.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `proton-mcp`: 65/100 (this document), [markdown](https://verifymcp.io/servers/vdeabreu-proton-mcp/proton-mcp.md), [page](https://verifymcp.io/servers/vdeabreu-proton-mcp/proton-mcp)

## Channel facts

- Registry: `pypi`
- Package: `proton-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - 1 of 28 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to vdeabreu/proton-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 763 tokens (~127/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Proton Mail MCP server?

Proton Mail runs locally as a PyPI package, launched with uvx proton-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add vdeabreu-proton-mcp -- uvx proton-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "vdeabreu-proton-mcp": {
      "command": "uvx",
      "args": [
        "proton-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vdeabreu-proton-mcp": {
      "command": "uvx",
      "args": [
        "proton-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add vdeabreu-proton-mcp -- uvx proton-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vdeabreu-proton-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "proton-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vdeabreu-proton-mcp --command uvx --arg proton-mcp
```

### Hermes

```yaml
mcp_servers:
  vdeabreu-proton-mcp:
    command: "uvx"
    args: ["proton-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "vdeabreu-proton-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "proton-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add vdeabreu-proton-mcp -t stdio -c uvx -a proton-mcp
```

### Other

```json
{
  "mcpServers": {
    "vdeabreu-proton-mcp": {
      "command": "uvx",
      "args": [
        "proton-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 65, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-20 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-19 (score 64, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-18 (score 78, +15)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.1.0 → 0.2.0

### 2026-11-17 (score 63)

First indexed and scored.

## MCP tools (6)

### `list_folders` (~34 tokens)

List every folder and label of the mailbox (labels appear as 'Labels/<name>', folders as 'Folders/<name>').

Output parameters:

- `result` (array)

### `list_emails` (~46 tokens)

List the most recent emails of a folder, newest first (headers only).

Input parameters:

- `folder` (string)
- `limit` (integer)
- `unread_only` (boolean)

Output parameters:

- `result` (array)

### `search_emails` (~119 tokens)

Search emails in a folder, newest first (headers only).

from_/to/subject/text are case-insensitive substring matches (text searches headers and body).
since/before are ISO dates (YYYY-MM-DD); before is exclusive.
The default folder 'All Mail' covers the whole mailbox.

Input parameters:

- `before`
- `folder` (string)
- `from_`
- `limit` (integer)
- `since`
- `subject`
- `text`
- `to`
- `unread_only` (boolean)

Output parameters:

- `result` (array)

### `read_email` (~57 tokens)

Read one email by its uid (from list_emails/search_emails, in the same folder). Does not mark it as read.

Input parameters:

- `folder` (string)
- `max_chars` (integer)
- `uid` (integer, required)

### `list_sender_addresses` (~58 tokens)

List the addresses send_email can send from, with the display name used for each.

The first one is the default for new emails; replies default to the address
the original email was sent to. Pass one as send_email's from_address.

Output parameters:

- `result` (array)

### `send_email` (~343 tokens)

Send an email (HTML + plain-text alternative) from the user's Proton address. IRREVERSIBLE.

Only call this after showing the user the exact sender, recipients, subject and
body and receiving their explicit approval in chat.
from_address picks which of the user's addresses sends it (see
list_sender_addresses). If omitted, new emails go out from the default address
and replies from the address the original was sent to.
The body is light Markdown, rendered to HTML: blank line = new paragraph,
single newline = line break, lines starting with "- " = bullet list,
"1. " = numbered list, **bold**, *italic*, [text](https://url). Don't use
headings, tables or raw HTML. Write the signature as the last paragraph.
to/cc/bcc accept comma-separated addresses ("Name <a@b.c>, d@e.f").
To reply, pass reply_to_uid (and reply_folder) of the original email: the reply
is threaded with it. Write the subject yourself (e.g. "Re: <original subject>").
Replies quote the original message below the body, like Proton does
("On <date>, <sender> wrote:" + quoted text); don't paste it into body
yourself. Pass include_original=False to leave it out.
A copy lands in the Sent folder automatically.

Input parameters:

- `bcc`
- `body` (string, required)
- `cc`
- `from_address`
- `include_original` (boolean)
- `reply_folder` (string)
- `reply_to_uid`
- `subject` (string, required)
- `to` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/vdeabreu-proton-mcp/proton-mcp#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 79
- 2026-11-19: 64
- 2026-11-18: 78
- 2026-11-17: 63

## Common questions

### What is the Proton Mail MCP server?

Proton Mail is an MCP server listed in the public MCP registry as io.github.vdeabreu/proton-mcp. Read, search and send Proton Mail through Proton Mail Bridge, with sending kept on approval. This page covers its PyPI package (proton-mcp).

### Is the Proton Mail MCP server safe to use?

Proton Mail scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Proton Mail MCP server expose?

Proton Mail exposes 6 tools: list_folders, list_emails, search_emails, read_email, list_sender_addresses, send_email. Their descriptions and schemas cost roughly 657 tokens of context every time the server is loaded.

### Is the Proton Mail MCP server still maintained?

Proton Mail is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Proton Mail MCP server under?

Proton Mail declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Proton Mail MCP server?

VerifyMCP ran 15 checks on Proton Mail, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Proton Mail: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/proton-mcp/
- Socket report: https://socket.dev/pypi/package/proton-mcp
- Repository: https://github.com/vdeabreu/proton-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vdeabreu-proton-mcp/proton-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/vdeabreu-proton-mcp/proton-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/vdeabreu-proton-mcp/proton-mcp.json
- HTML version of this page: https://verifymcp.io/servers/vdeabreu-proton-mcp/proton-mcp
