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 分

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