Securessmtp

com.securessmtpPublished by securessmtp.comOfficial publisherv1.0.0Updated Oct 24, 2026

Send email, manage sending domains, and read delivery analytics from your SecureSMTP account.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Remote SecureSMTP server that lets an assistant send transactional email, manage sending domains and read delivery analytics for one site account.

What you can do
  • Send transactional email through the account's sending pipeline, subject to the same quota, spam scoring and suppression as the API
  • Inspect the account: plan tier, email quota used, limit and remaining, and number of sending domains
  • List sending domains with their verification status, add a new domain and get the DNS records to publish, then verify SPF/DKIM
  • Read deliverability counts for the last 30 days, such as delivered, opened and bounced
When to use it
Useful when you want an assistant to draft and send transactional mail, set up or check a sending domain's DNS verification, or report on recent delivery performance without leaving the chat.
Requirements
A remote Streamable HTTP endpoint; no local package needed. Authentication is required: OAuth 2.1 with browser approval and site selection, or a site API key sent as an Authorization Bearer header. A SecureSMTP account with a site is needed, and stdio-only clients need an mcp-remote bridge. claude.ai custom connectors require a paid plan.
Before you install
The assistant can send real email and add sending domains, which changes account state and consumes quota. The site API key is a credential that grants access to that site's account; store it carefully. OAuth grants access to whichever site is chosen at consent. Every tool is limited to the single site the connection is scoped to.

Installation

In SourceWeft

  1. Open Securessmtp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.securessmtp%2Fsecuressmtp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "securessmtp": {
      "type": "http",
      "url": "https://securessmtp.com/api/mcp"
    }
  }
}

README

SecureSMTP MCP server

Connect SecureSMTP to Claude and other MCP clients. Send transactional mail, manage sending domains, and read delivery analytics for your account — in natural language.

  • Endpoint: https://securessmtp.com/api/mcp (Streamable HTTP)
  • Auth: OAuth 2.1 (one-click, recommended) or a site API key as a Bearer token
  • Cost: free — every call runs against your own account and stays within your plan limits

What it can do

ToolWhat it does
get_accountPlan tier, email quota (used / limit / remaining), number of sending domains
list_sending_domainsList the account's sending domains and their verification status
add_sending_domainAdd a sending domain; returns the DNS records to publish
verify_domainVerify a sending domain's DNS (SPF / DKIM)
get_deliverabilityDelivery status counts for the last 30 days (delivered / opened / bounced / …)
send_emailSend a transactional email — enforces the same quota, spam scoring, and suppression as the API

Every tool is scoped to a single site, so a connection can only ever see or act on that account.

Connect from Claude Code

OAuth (opens a browser to approve):

bash
claude mcp add --transport http securessmtp https://securessmtp.com/api/mcp

Or with a site API key (no browser step):

bash
claude mcp add --transport http securessmtp https://securessmtp.com/api/mcp \  --header "Authorization: Bearer <your-site-api-key>"

Connect from claude.ai (custom connector)

Requires a claude.ai Pro/Team/Enterprise plan (custom connectors are not available on the free tier).

  1. Settings → Connectors → Add custom connector
  2. URL: https://securessmtp.com/api/mcp
  3. Approve access when the SecureSMTP consent screen appears, and pick which site to grant.

Where to get an API key

Sign in at securessmtp.com, open a site, and copy its API key — the same key the WordPress plugin and REST API use.

How auth works

  • OAuth 2.1 with PKCE and dynamic client registration. Discovery lives at /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server. Access tokens are short-lived; refresh tokens rotate.
  • API key — send the site key as Authorization: Bearer <key>.

Links

Connect from any MCP client

The server is remote (Streamable HTTP). Use OAuth (a browser approval) or send your site API key as a Bearer header. Endpoint: https://securessmtp.com/api/mcp

Claude Code (CLI)

bash
claude mcp add --transport http securessmtp https://securessmtp.com/api/mcp# with an API key instead of OAuth:claude mcp add --transport http securessmtp https://securessmtp.com/api/mcp \  --header "Authorization: Bearer <your-site-api-key>"

Cursor — ~/.cursor/mcp.json (or .cursor/mcp.json in a project)

json
{  "mcpServers": {    "securessmtp": {      "url": "https://securessmtp.com/api/mcp"    }  }}

With an API key instead of OAuth, add headers:

json
{  "mcpServers": {    "securessmtp": {      "url": "https://securessmtp.com/api/mcp",      "headers": { "Authorization": "Bearer <your-site-api-key>" }    }  }}

VS Code (GitHub Copilot) — .vscode/mcp.json

json
{  "servers": {    "securessmtp": {      "type": "http",      "url": "https://securessmtp.com/api/mcp"    }  }}

Codex CLI, Claude Desktop, Windsurf, Cline (stdio clients)

Clients that only speak stdio connect through the mcp-remote bridge, which also handles the OAuth browser flow for you.

Codex CLI — ~/.codex/config.toml:

toml
[mcp_servers.securessmtp]command = "npx"args = ["-y", "mcp-remote", "https://securessmtp.com/api/mcp"]

Claude Desktop / Windsurf / Cline — the JSON mcpServers block:

json
{  "mcpServers": {    "securessmtp": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://securessmtp.com/api/mcp"]    }  }}

Getting an API key

Sign in at securessmtp.com, open a site, and copy its API key. OAuth needs no key — you approve access in the browser and pick which site to grant.

Source: README.md at commit e2211f8

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 28, 2026

Score

75% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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
  • License10 pts

    Declare a license in the repository or the registry entry.