English Français العربية

io.github.closermethod/outreach-deliverability-mcp

Official registry Security

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

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package outreach-deliverability-mcp
Claude Code 
claude mcp add outreach-deliverability-mcp -- npx -y outreach-deliverability-mcp@1.0.2
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "outreach-deliverability-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "outreach-deliverability-mcp@1.0.2"
            ]
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Outreach Deliverability MCP
  2. Why This Exists
  3. 6 Tools
  4. Sample Use
  5. Works With
  6. Built By

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

// 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

Frequently asked questions

What is io.github.closermethod/outreach-deliverability-mcp?

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

How do I install io.github.closermethod/outreach-deliverability-mcp?

It runs on your machine. In Claude Code: claude mcp add outreach-deliverability-mcp -- npx -y outreach-deliverability-mcp@1.0.2. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.closermethod/outreach-deliverability-mcp need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is io.github.closermethod/outreach-deliverability-mcp open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains io.github.closermethod/outreach-deliverability-mcp?

It is published by closermethod. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.