Proton Mail
PYPI · PROTON-MCP
Read, search and send Proton Mail through Proton Mail Bridge, with sending kept on approval.
Available components
Last scanned (11 hours ago)
Scores higher than 57% of PyPI servers
Category Communication
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. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to vdeabreu/proton-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 20 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.0 → 0.2.0 functional
- 17 Nov 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/proton-mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | vdeabreu/proton-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/vdeabreu/proton-mcp/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 3970329735 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:bee33deee183d6eee54470373dac4d9889b79a2d4ca8768817ad2e43632be4c7 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_emails ~46
List the most recent emails of a folder, newest first (headers only).
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | – |
| limit | integer | – | – |
| unread_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_folders ~34
List every folder and label of the mailbox (labels appear as 'Labels/<name>', folders as 'Folders/<name>').
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_sender_addresses ~58
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
read_email ~57
Read one email by its uid (from list_emails/search_emails, in the same folder). Does not mark it as read.
| Name | Type | Req | Description |
|---|---|---|---|
| folder | string | – | – |
| max_chars | integer | – | – |
| uid | integer | yes | – |
No output schema declared.
No examples provided.
search_emails ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| before | – | – | – |
| folder | string | – | – |
| from_ | – | – | – |
| limit | integer | – | – |
| since | – | – | – |
| subject | – | – | – |
| text | – | – | – |
| to | – | – | – |
| unread_only | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
send_email ~343
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bcc | – | – | – |
| body | string | yes | – |
| cc | – | – | – |
| from_address | – | – | – |
| include_original | boolean | – | – |
| reply_folder | string | – | – |
| reply_to_uid | – | – | – |
| subject | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
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.
pypi · proton-mcp
claude mcp add vdeabreu-proton-mcp -- uvx proton-mcp
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.