Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Proton Mail (unofficial)

NPM · PROTON-MAIL-MCP · SCANNED SEP 21

Unofficial Proton Mail MCP — send, read, search & organize email over SMTP and IMAP

Available components

npm · proton-mail-mcp 44
0 this week 44 Trust /100
Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects nodemailer 8.0.11, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 42 of 151 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 sethbang/proton-mail-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 113 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the Proton Mail (unofficial) MCP server?

Proton Mail (unofficial) runs locally as an npm package, launched with npx -y proton-mail-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · proton-mail-mcp

# add to Claude Code
claude mcp add sethbang-proton-mail-mcp -- npx -y proton-mail-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "sethbang-proton-mail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "proton-mail-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "sethbang-proton-mail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "proton-mail-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add sethbang-proton-mail-mcp -- npx -y proton-mail-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sethbang-proton-mail-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "proton-mail-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add sethbang-proton-mail-mcp --command npx --arg -y --arg proton-mail-mcp
# ~/.hermes/config.yaml
mcp_servers:
  sethbang-proton-mail-mcp:
    command: "npx"
    args: ["-y", "proton-mail-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "sethbang-proton-mail-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "proton-mail-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add sethbang-proton-mail-mcp -t stdio -c npx -a -y proton-mail-mcp
// mcp.json
{
  "mcpServers": {
    "sethbang-proton-mail-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "proton-mail-mcp"
      ]
    }
  }
}
Changelog

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.

  • 18 Sept 26 0
    • CVE-2026-92598 affects this package: high ▼ security
    • CVE-2026-92595 affects this package: high ▼ security
    • CVE-2026-92597 affects this package: high ▼ security
    • CVE-2026-92596 affects this package: high ▼ security
    • GHSA-cc9r-2j5m-2m83 no longer affects this package ▲ security
    • GHSA-8m3c-c648-2xjj no longer affects this package ▲ security
    • GHSA-wmmp-3585-3rmp no longer affects this package ▲ security
    • GHSA-2x7j-588g-ccc2 no longer affects this package ▲ security
  • 15 Sept 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 14 Sept 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 9 Sept 26 0
    • GHSA-8m3c-c648-2xjj affects this package: high ▼ security
    • GHSA-2x7j-588g-ccc2 affects this package: high ▼ security
    • GHSA-cc9r-2j5m-2m83 affects this package: high ▼ security
    • GHSA-wmmp-3585-3rmp affects this package: high ▼ security
  • 2 Sept 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 1 Sept 26 0
    • CVE-2026-82659 affects this package: high ▼ security
    • GHSA-p6gq-j5cr-w38f no longer affects this package ▲ security
    • Security disclosure: pass → unverified ▼ functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Aug 26 0
    • CVE-2026-40345 no longer affects this package ▲ security
Diagnostics

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 Sept 2026 · Analysed npm/proton-mail-mcp@1.0.2

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 npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo sethbang/proton-mail-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/sethbang/proton-mail-mcp/.github/workflows/publish.yml@refs/tags/v1.0.2
Rekor log index 1675392747
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:5c8ba6deab1d4bd558655d3fe317cbd396dc0445743b88b252467fe626c81ebaaccb74bbd554646c33806ec050fc859b4aca9348deae8971eef1addd8

Background: How many MCP packages publish verified provenance →

Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-2x7j-588g-ccc2 CVE-2026-92596 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8m3c-c648-2xjj CVE-2026-92595 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-cc9r-2j5m-2m83 CVE-2026-92597 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-p6gq-j5cr-w38f CVE-2026-82659 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N yes
GHSA-wmmp-3585-3rmp CVE-2026-92598 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 151 packages
Packages resolved 151
Stale 42
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the Proton Mail (unofficial) MCP server?

Proton Mail (unofficial) is an MCP server listed in the public MCP registry as io.github.sethbang/proton-mail-mcp. Unofficial Proton Mail MCP, send, read, search & organize email over SMTP and IMAP. This page covers its npm package (proton-mail-mcp).

Is the Proton Mail (unofficial) MCP server safe to use?

Proton Mail (unofficial) scores 44 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 21 September 2026. It declares no install or post-install scripts. 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.

Is the Proton Mail (unofficial) MCP server still maintained?

Proton Mail (unofficial) is still listed as active in the MCP registry. We last reached this channel on 21 September 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 (unofficial) MCP server under?

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