Salamailer MCP server

Read from the package source without running it. The installed server may list more.

• delete_contactwrite action

  Forget a recipient’s saved standing passphrase. Future sends to them will auto-generate a fresh passphrase again.

• get_account_status

  Get the sending account status and quotas: plan, whether sending is allowed (and why not), trial sends left, and SMS remaining this period.

• get_delivery_receipt

  Get the exportable, metadata-only delivery receipt for a message (audit evidence of delivery and opening).

• list_contacts

  List recipients that have a saved standing passphrase (emails and labels only; the passphrases themselves are never returned).

• list_replies

  List inbound secure replies from recipients (id, from, read/unread, date). Replies are end-to-end encrypted; use read_reply to decrypt one locally.

• list_sent_messages

  List sent secure messages with status (sent/opened/expired/revoked), recipient, and expiry.

• read_reply

  Decrypt an inbound secure reply locally (the server only ever held ciphertext). Returns the reply text and attachment names; pass save_dir to write the attachments to disk (must be inside the attachment root).

• resend_notification

  Re-send the notification email for a sent message. The open link is reconstructed locally from the sender key; the server never stores the key.

• resend_sms_code

  Issue and send a fresh one-time SMS gate code for an SMS-gated message (e.g. after the recipient locked themselves out). Counts against the SMS quota.

• revoke_message

  Revoke a sent message: permanently deletes the ciphertext so the link stops working. Irreversible.

• save_contact

  Save a standing gate passphrase for a recipient so every future send to them reuses the same passphrase (they only learn it once). Stored encrypted under your vault key; the server can never read it. Ideal for a regular correspondent you message often.

• send_secure_messagewrite action

  Send an end-to-end encrypted message (and optional file attachments) to any email address.

• Code scan3 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenanceno repository listed3/15
• Maintainer identityverified namespace with website, no repo4/10

Safety score

68/100

higher than 35% of 916 Email servers

Tools

12

the typical Email server has 7

Tools that change things

17%

typical: 25%. Fewer write tools means less an agent can break

Downloads a week

27

more than 10% of 235 Email servers with a package

Salamailer: common questions

Is Salamailer MCP server safe?

With care: it is graded C, so read the findings first (68/100). Read the Salamailer safety report

How do I install Salamailer?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Salamailer need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Salamailer maintained?

The latest release is v1.0.0.

What can I use instead of Salamailer?

Servers from other publishers that do the same job: Sendsoon MCP server, Agent Relay MCP server and LMCP MCP server.

How does Salamailer compare with other Email MCP servers?

safety score 68/100 (higher than 35% of 916 Email servers); tools 12 (the typical Email server has 7); tools that change things 17% (typical: 25%. Fewer write tools means less an agent can break). Full comparison.