Loading the registry…
MCP server exposing Proton Mail (via Proton Mail Bridge IMAP) with read access and multi-account support.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- proton-mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
7 findings · 6.9s
v0.3.74
4 findings · 1.3s
v0.1.0
0 findings · 3.1s
v0.1.0
1 finding · 3.1s
v0.71.0
0 findings · 0.2s
v2.3.8
0 findings · 1.3s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.7s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged91 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 12 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 7 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
4 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: opt.nerlo-rules.nerlo-install-pipe-to-shell, AAK-AGENT-002, PIPELINE_TAINT_FLOW and 1 more · Files: /repo/AGENTS.md, AGENTS.md · reported by nerlo-install-instruction, agent-audit-kit, cisco-skill-scanner
The model could have called any of these a false positive and did not.
1 AAK-OAUTH-3P-001
Files: pyproject.toml · reported by agent-audit-kit
7 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: SECRET_PASSWORD_VAR, AAK-SEC-MD-001, PIPELINE_TAINT_FLOW and 2 more · Files: /repo/src/proton_mcp_server/config.py, SECURITY.md, /repo/SKILL.md · reported by cisco-skill-scanner, agent-audit-kit
Medium concern for credential exposure and data flow issues.
The artifact contains findings indicating potential credential exposure, specifically related to password variables and OAuth configurations. Data flow issues were also identified, which could lead to information disclosure. Additionally, general security weaknesses and other medium-severity concerns are present.
Concern level assessed by the review: Medium. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.