Outreach Deliverability Mcp

io.github.closermethod由 GitHub 帳號 closermethod 發布v1.0.2更新於 Oct 24, 2026

Channel-safety for cold outreach: volume limits, SPF/DKIM/DMARC, spam-trigger auditing.

已驗證STDIO僅桌面溝通與協作商業與電商

概覽

AI 產生的概覽

一個本機 MCP 伺服器，為助理提供冷開發外聯的通道安全指引：發送量限制、寄件者設定、垃圾郵件觸發稽核與活動診斷。

可以做什麼
取得電子郵件、LinkedIn、Instagram 私訊與 X 私訊各通道的規則：安全每日發送量、帳號設定、暖機、危險訊號與法律基礎。取得十步冷郵件基礎設施清單，涵蓋網域、SPF、DKIM、DMARC、信箱、暖機、名單驗證與監控。稽核文案中的垃圾郵件觸發詞並給出 0-100 風險分數。將開啟率、回覆率、退信率與接受率基準與觀測值對照解讀。診斷失敗層級（基礎設施、名單或文案）及修復順序。以單一承載內容回傳完整資料庫，供助理取得完整脈絡。
適用情境
在規劃或檢視冷開發外聯活動時使用，讓助理在發送前檢查發送量、寄件者驗證設定與文案。它僅提供建議，不發送任何內容。
執行需求
透過 stdio 以本機程序執行，從 npm 套件 outreach-deliverability-mcp 安裝，需要 Node.js。未宣告帳號、API 金鑰、環境變數或標頭。僅限桌面端。
安裝前請注意
它回傳規則、清單與稽核結果而不發送訊息，因此本身不會聯絡收件者。README 說明平台限制與過濾行為經常變動，其數值是保守的實務範圍而非平台保證，法律說明僅為方向性提示而非法律建議。應將其輸出視為需核實的指引，而非權威政策。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Outreach Deliverability Mcp，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Outreach Deliverability MCP

The channel-safety layer for cold outreach. Volume discipline, sender setup, spam auditing — so good messages actually arrive.

Disclaimer. Platform limits and filtering behavior change frequently; values are conservative practitioner ranges as of last verification, not platform guarantees. Legal notes (CAN-SPAM / GDPR / PECR / CASL) are orientation, not legal advice.

Why This Exists

Most outbound fails before the copy is ever read. Burned domains, throttled LinkedIn accounts, and spam-foldered sends kill campaigns that any message audit would have passed. AI agents make this worse: they can generate 500 perfect emails an hour, and sending them is exactly how you lose the domain.

This MCP is the layer that keeps the channel alive. It does NOT send anything — it returns rules, checklists, and audits that an agent consults BEFORE and DURING a campaign.

The core diagnostic it encodes: deliverability problems masquerade as copy problems. A 1% reply rate usually isn't a bad hook — it's a foldered send. Fix order: infrastructure → list → message.

6 Tools

ToolWhat it returns
get_channel_rulesSafe daily volumes, account setup, warmup protocol, kill signals, personalization floor, and legal basics per channel: email, LinkedIn, Instagram DM, X DM
get_sender_setup_checklistThe 10-step cold-email infrastructure checklist: lookalike domains, SPF, DKIM, DMARC, mailboxes, warmup, list verification, tracking, compliance, monitoring
audit_spam_triggersCopy audit: 30+ flagged phrases, all-caps, exclamations, link count, attachments, money symbols, fake Re:/Fwd: — with a 0-100 risk score
interpret_benchmarkHealthy/warning ranges for open rate, reply rate, bounce rate, LinkedIn acceptance, DM reply — with an optional direct read of your observed value
diagnose_campaignGiven your observed metrics, names the failure layer (infrastructure vs list vs message) and the fix order
get_full_packThe complete library as one payload for full agent context

Sample Use

typescript
// Campaign feels dead. Copy problem or channel problem?mcp.call("diagnose_campaign", {  channel: "email", open_rate: 31, reply_rate: 0.8, bounce_rate: 4.2});// Returns: failure layer = LIST. Bounce 4.2% > 3% is actively damaging the// domain; open 31% says sends are being foldered. Fix infrastructure and// list BEFORE touching the copy.
mcp.call("audit_spam_triggers", { text: "URGENT: Don't miss this LIMITED TIME offer!!! Click here..." });// Returns: HIGH RISK, phrase + structural hits itemized.

Works With

Pair with outbound-engine-mcp: that one makes the message worth sending; this one makes sure it lands.

Built By

Elisabeth Hitz — 10+ years of B2B enterprise sales experience across ad-tech, SaaS, media, and global hiring. Now building MCP servers for the AI agent ecosystem.

License: MIT

來源：README.md，提交 58c6214

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v1.0.2最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

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