
Zerosmtp
io.github.msgwingPublished by GitHub account msgwingv1.0.2Updated Oct 27, 2026
A free SMTP relay that still takes a username and password, for devices that cannot do OAuth 2.0.
Overview
Local stdio MCP server for Zerosmtp, a free SMTP relay that accepts a username and password for devices that cannot use OAuth 2.0.
- What you can do
- The listing provides no tool list, instructions or README, so the exact tools are unknown.
- Based on the description, it relates to sending mail through a free SMTP relay that authenticates with a username and password instead of OAuth 2.0.
- It is intended for devices or clients that cannot perform OAuth 2.0 sign-in.
- When to use it
- Consider it if you need an assistant to work with an SMTP relay that uses plain username and password credentials, for example on a device or client that cannot do OAuth 2.0. Because no tools are documented, verify what it actually exposes before relying on it.
- Requirements
- Runs as a local process over stdio, installed from the npm package zerosmtp-mcp, so a Node.js runtime is needed. The manifest declares no authentication, environment variables or headers, but the relay itself is described as taking a username and password, so credentials are likely needed and must be supplied some other way.
Installation
In SourceWeft
- Open Zerosmtp in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.2LatestSep 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.