proton-safe-mcp@2.3.2
VERIFIED· not startedPublisher claims: "Client-agnostic Proton Mail MCP server with safe reads, bounded attachment text extraction, and explicitly confirmed drafts" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
PROTON_BRIDGE_PASSWORDConfiguration, not credentials: CODEX_HOME, DISPLAY, PROTON_BRIDGE_ALIASES, PROTON_BRIDGE_USER, PROTON_MCP_STATE_DIR, WAYLAND_DISPLAY- Where it talks to
- no vendor host named in the codeAlso proton.me, chatgpt.com, microsoft.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names proton.me, chatgpt.com, microsoft.com as well as its own vendor. The guard injects PROTON_BRIDGE_PASSWORD only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-15 and scored it 80/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
process = subprocess.Popen( # noqa: S603 - fixed argv, no shellFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."Enter the password generated by Bridge.",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Tunnel permissions belong to the OpenAI Platform organization, while ChatGPT Developer mode is aFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.chmod 0755 "$STAGE/DEBIAN/postinst" "$STAGE/DEBIAN/postrm"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.1. Enable Developer mode under **Settings → Security and login**.Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.4. verify Developer mode and tunnel-use permission for the ChatGPT account;Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.completed = subprocess.run( # noqa: S603 - fixed argv, no shell, boundedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.find "$STAGE/opt" -type d -exec chmod 0755 {} +Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.so a draft is never refused over it after the user already confirmed one.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.1. Enable Developer mode under **Settings → Security and login**.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.4. verify Developer mode and tunnel-use permission for the ChatGPT account;Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.1. Enable Developer mode under **Settings → Security and login**.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Tunnel permissions belong to the OpenAI Platform organization, while ChatGPT Developer mode is aFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for proton-safe-mcp@2.3.2 as of 12 min ago. This is the package itself, not its dependencies.