Salamailer

fi.salamailerPublished by salamailer.fiv1.0.0Updated Oct 24, 2026

Send end-to-end encrypted email and files. Encryption happens on your machine, not our server.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

A local MCP server that lets an assistant send end-to-end encrypted email and files, with encryption performed on the user's own machine.

What you can do
Salamailer is a local MCP server for sending end-to-end encrypted email and files. According to its registry description, encryption happens on the user's machine rather than on the provider's server. The manifest lists no tools, so the exact operations an assistant can invoke are not documented here.
When to use it
Consider it when an assistant needs to send email or files with end-to-end encryption and you want the encryption to happen locally. It is a desktop-only local process, so it is not suitable for browser or hosted use.
Requirements
Runs as a local process on the user's machine via the npm package salamailer over stdio. Desktop only; no web executable. The manifest declares no authentication, environment variables, or headers, but the actual credentials or keys needed for encrypted sending are not documented in the provided material.
Before you install
The description says encryption happens on your machine, but no details are given about key management, recipients, or what metadata leaves the machine. No tools, credentials, or environment variables are documented, so verify what the server sends and where before relying on it for sensitive mail.

Installation

In SourceWeft

  1. Open Salamailer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.