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 分

    請在儲存庫或註冊中心條目中宣告授權條款。