Securessmtp

com.securessmtp由 securessmtp.com 发布官方发布者v1.0.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行沟通与协作商业与电商

概览

AI 生成的概览

远程 SecureSMTP 服务器，让助手为单个站点账户发送事务邮件、管理发信域名并查看投递分析。

可以做什么
  • 通过账户的发信流程发送事务邮件，与 API 一样受配额、垃圾邮件评分和抑制名单约束
  • 查看账户信息：套餐等级、邮件配额已用/上限/剩余，以及发信域名数量
  • 列出发信域名及验证状态，添加新域名并返回需发布的 DNS 记录，再验证 SPF/DKIM
  • 读取最近 30 天的投递统计，如已投递、已打开、退信等
适用场景
适合让助手在对话中起草并发送事务邮件、配置或检查发信域名的 DNS 验证，或汇报近期投递表现时使用。
运行要求
需要远程 Streamable HTTP 端点，无需本地安装包。必须认证：OAuth 2.1（浏览器授权并选择站点），或以 Authorization Bearer 头传入站点 API 密钥。需要 SecureSMTP 账户及站点；仅支持 stdio 的客户端需借助 mcp-remote 桥接。claude.ai 自定义连接器需付费套餐。
安装前请注意
助手可发送真实邮件并添加发信域名，会改变账户状态并消耗配额。站点 API 密钥是可访问该站点账户的凭据，需妥善保管。OAuth 授权范围取决于同意时选择的站点。所有工具仅限连接所绑定的单个站点。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Securessmtp，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.securessmtp%2Fsecuressmtp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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.

来源：README.md，提交 e2211f8

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Sep 28, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。