Protonmail (barhatch) MCP Server

protonmail-mcp-server npm v1.0.1 Source verified

Published by barhatch — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Professional ProtonMail MCP server with 23 tools for email management, folder operations, analytics, and seamless Proton Bridge integration.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/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
A Why this grade threat 100 − adoption risk = 94/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 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. 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

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 1

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([get_logs]) and tools that can send data out ([send_email]) are exposed together. An agent can move private data to the sink.

Evidence: sources [get_logs] → sinks [send_email]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow get_logs → send_email

Tools 25

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

  • get_logsreads sensitive data
  • send_emailnetwork egress
  • add_labelno sensitive capability
  • bulk_add_labelno sensitive capability
  • bulk_move_emailsno sensitive capability
  • clear_cacheno sensitive capability
  • create_folderno sensitive capability
  • delete_emailno sensitive capability
  • delete_folderno sensitive capability
  • get_connection_statusno sensitive capability
Show 15 more tools ↓
  • get_contactsno sensitive capability
  • get_email_analyticsno sensitive capability
  • get_email_by_idno sensitive capability
  • get_email_statsno sensitive capability
  • get_emailsno sensitive capability
  • get_foldersno sensitive capability
  • get_volume_trendsno sensitive capability
  • mark_email_readno sensitive capability
  • move_emailno sensitive capability
  • rename_folderno sensitive capability
  • search_emailsno sensitive capability
  • send_test_emailno sensitive capability
  • star_emailno sensitive capability
  • sync_emailsno sensitive capability
  • sync_foldersno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

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.1 latest A 94/100 1 1.13.0 2026-09-07

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: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/protonmail-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/protonmail-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/protonmail-mcp-server"><img src="https://mcptrustchecker.com/registry/protonmail-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/protonmail-mcp-server/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 protonmail-mcp-server --online

Use the free API → How scoring works

Other implementations of Protonmail 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Web, Search & Scraping