Skip to content

MCP servers › io.github.Alexendros › proton-mail-mcp

MCP server · registry snapshot 2026-10-04

io.github.Alexendros/proton-mail-mcp

Proton Mail MCP via Bridge (IMAP/SMTP) · 13 tools · dual transport stdio + HTTP. — the publisher's description

Topic: communication-and-social · AI-classifiedversion 0.1.2TypeScriptstandard input/output

Summary

io.github.Alexendros/proton-mail-mcp is a local MCP server listed in the official MCP registry at version 0.1.2. We have not tested it. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.

Key facts

Runs
local package
Transport
standard input/output
Package
npm · listed version package does not exist
Repository
public
Topic
communication-and-socialAI-classified
Last tested
not tested

Worth knowing before you connect it

  • The listed package does not exist on npm, so an install from the registry entry fails.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
no
Last tested
not tested
Registry data
snapshot 2026-10-04
Package and repository
checked 2026-10-06

Security testing

Has it been tested?

Feature #1

It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.

Required inputs the publisher declares: PROTON_USERNAME, PROTON_PASSWORD (secret).

What it is

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 0.1.2 on npmpackage does not existdiffersnpm · 2026-10-06
Repository github.com/Alexendros/proton-mail-mcpOpens publiclymatchesapi.github.com · 2026-10-06

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.1.2
Status
package does not exist

Source: registry.npmjs.org · 2026-10-06. About the version the registry lists; a manual install may resolve to a different one.

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.Alexendros
GitHub owner
an organization (Soluciones-Alexendros)
Repository
github.com/Alexendros/proton-mail-mcp
Stars
0
Repository age
91–180 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-06.

Choosing

Common questions about io.github.Alexendros/proton-mail-mcp

Answered from the data above

Has io.github.Alexendros/proton-mail-mcp been security tested?

Not yet. It requires a credential (a key or token) that the publisher marks as required. We never fill in credentials, so we did not start it.

Is the listed version current?

The listed version cannot be installed: package does not exist.

Where is the source code of io.github.Alexendros/proton-mail-mcp?

In github.com/Alexendros/proton-mail-mcp, which opens publicly.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
communication-and-social
AI-classified · 2026-10-08
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
TypeScript
api.github.com · 2026-10-08
Hosting type
local package
registry · 2026-10-04
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-10-04
Required credentials
requires a secret
registry · no declaration is not a guarantee
Package registry
npm
registry · 2026-10-04
Freshness
91–180 days
registry updatedAt · 2026-10-04
Lifecycle status
active
registry · 2026-10-04
License class
not stated
npm returned HTTP 404 for @alexendros/proton-mail-mcp@0.1.2
Integrity hash
not stated
npm returned HTTP 404 for @alexendros/proton-mail-mcp@0.1.2
Signature / provenance
not stated
npm returned HTTP 404 for @alexendros/proton-mail-mcp@0.1.2
Dependency advisories
not stated
package/version not found on npm, so no tree can be resolved
Popularity
not stated
npm returned HTTP 404 for @alexendros/proton-mail-mcp@0.1.2
Publisher signals
owner: an organization · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-10-06
Maintenance
active
api.github.com · 2026-10-06
Environment
your machine
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Alexendros/proton-mail-mcp: MCP server record.” Data checked 2026-10-06. https://protocolprobe.com/mcp/servers/io.github.Alexendros/proton-mail-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can authorize a full test.

Write to hello@protocolprobe.com · corrections log · methodology