MCP.Market

Outreach Deliverability MCP server

by closermethod·io.github.closermethod/outreach-deliverability-mcp·v1.0.2
No reviews yet

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

A85/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
New

0 stars40 downloads/wk

Reviews

Write one

Nobody has reviewed Outreach Deliverability yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Outreach Deliverability tools (6)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • audit_spam_triggers

    Audit outreach copy (subject + body) for spam-filter triggers: flagged phrases, all-caps, exclamation marks, multiple links, attachments, money symbols, fake Re:/Fwd: subjects. Returns hits, a 0-100 risk score, and a verdict.

  • diagnose_campaign

    Given observed campaign metrics (any of: open_rate, reply_rate, bounce_rate, acceptance_rate as percents), returns the most likely failure layer (infrastructure vs list vs message) and the fix order. Deliverability problems masquerade as copy problems — this tool tells you which one you have.

  • get_channel_rules

    Get safe volume limits, account setup, warmup protocol, kill signals, personalization floor, and legal basics for an outreach channel. Channels: email, linkedin, instagram_dm, x_dm.

  • get_full_pack

    Returns the complete deliverability library: channel rules, sender setup, spam triggers, benchmarks. Useful for full agent context.

  • get_sender_setup_checklist

    Returns the 10-step cold-email infrastructure checklist: lookalike domains, SPF, DKIM, DMARC, mailbox provisioning, warmup, list verification, tracking domains, compliance footer, monitoring.

  • interpret_benchmark

    Interpret an outreach metric against practitioner benchmarks: email_open_rate, email_reply_rate, email_bounce_rate, linkedin_acceptance_rate, dm_reply_rate. Returns healthy range, warning threshold, and the diagnostic note.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan3 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 73 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Outreach Deliverability compares

Against every graded Sales and outbound MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 76% of 876 Sales and outbound servers
Tools
6
the typical Sales and outbound server has 8
Tools that change things
0%
typical: 11%. Fewer write tools means less an agent can break
Downloads a week
40
more than 33% of 156 Sales and outbound servers with a package

What its tools let an agent do: 6 read

Install Outreach Deliverability in Claude Code, Cursor or VS Code

Runs npx -y outreach-deliverability-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add outreach-deliverability-mcp -- npx -y outreach-deliverability-mcp
Add to Cursor

What the publisher says

From the Outreach Deliverability repository's README, as published. We do not edit it. Read it on GitHub

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

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

Nothing above is checked by us. What we check is on the safety report.

Outreach Deliverability: common questions

Is Outreach Deliverability MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Outreach Deliverability safety report
How do I install Outreach Deliverability?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Outreach Deliverability need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Outreach Deliverability maintained?
The last commit was 113 days ago (2026-07-14). The latest release is v1.0.2.
What can I use instead of Outreach Deliverability?
Servers from other publishers that do the same job: LinkedIn MCP Server (Salesbot), MisarReach MCP Server and HeyLead — AI agent for LinkedIn outreach MCP server.
How does Outreach Deliverability compare with other Sales and outbound MCP servers?
safety score 85/100 (higher than 76% of 876 Sales and outbound servers); tools 6 (the typical Sales and outbound server has 8); tools that change things 0% (typical: 11%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Outreach Deliverability

Same job from other publishers: the closest match first, then the best rated.

  • LinkedIn MCP Server (Salesbot)
    Human-in-the-loop LinkedIn outreach and a built-in sales CRM for AI agents. Safety-gated, anti-spam.
    B
  • MisarReach MCP Server
    Find leads, enrich and score them, run multi-channel outreach, and manage the sales pipeline — from…
    A
  • HeyLead — AI agent for LinkedIn outreach
    AI agent for LinkedIn outreach: finds the right people, writes in your voice, follows up, replies.
    A
  • Vibe Prospecting
    B2B company and contact data for lead lists, enrichment, research, and outreach. OAuth sign-in.
    A
  • Omentir
    Find LinkedIn prospects, draft outreach, and run human-paced campaigns from your AI agent.
    A

More from closermethod →