Pipefire email deliverability tools

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Free email deliverability tools: SPF, DKIM, DMARC, blacklist and header checks, cold email scoring.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Pipefire email deliverability tools": {
      "url": "https://pipefire.ai/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (16)

• check_domain_email_setup read-only

  Check whether a domain is set up to send and receive email properly: MX, SPF, DKIM and DMARC in one go, each with pass/warn/fail, what was found, and how to fix it. Use when someone asks why their email goes to spam, whether their domain is set up right, or before sending cold email.

  Parameters:

  • domain (required) — string — The domain to check, e.g. example.com.
  • selector — string — DKIM selector if known. Common ones are tried automatically.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_dmarc read-only

  Check a domain's DMARC record: whether one exists at _dmarc, its policy (none, quarantine, reject), whether reports are collected, and outdated tags. Tells you whether the domain can be impersonated by email.

  Parameters:

  • domain (required) — string — The domain to check, e.g. example.com. A URL or email address also works.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_spf read-only

  Check a domain's SPF record: whether it exists, is valid, stays under the 10 DNS lookup limit, and ends with a sensible all mechanism.

  Parameters:

  • domain (required) — string — The domain to check, e.g. example.com. A URL or email address also works.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_dkim read-only

  Look up a domain's DKIM public key, trying the selectors Google Workspace, Microsoft 365 and common senders use, plus one you name.

  Parameters:

  • domain (required) — string — The domain to check, e.g. example.com. A URL or email address also works.
  • selector — string — DKIM selector if known (e.g. google, selector1). Common ones are tried automatically.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_mx read-only

  List a domain's mail servers (MX records) and which provider handles its email.

  Parameters:

  • domain (required) — string — The domain to check, e.g. example.com. A URL or email address also works.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_bimi read-only

  Check a domain's BIMI record (logo in the inbox) and whether its DMARC policy is strict enough for BIMI to show.

  Parameters:

  • domain (required) — string — The domain to check, e.g. example.com. A URL or email address also works.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_mta_sts read-only

  Check a domain's MTA-STS policy, which forces encrypted delivery of incoming mail.

  Parameters:

  • domain (required) — string — The domain to check, e.g. example.com. A URL or email address also works.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• check_blacklists read-only

  Check whether a domain's sending IPs, or a single IPv4 address, are listed on the major email blacklists (Spamhaus, Barracuda, SpamCop and others), with removal links.

  Parameters:

  • target (required) — string — A domain (example.com) or a public IPv4 address.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• analyze_email_headers read-only

  Read the raw headers of a received email: SPF, DKIM and DMARC results, alignment, the delivery path and delays. Use when someone pastes headers and asks why a message went to spam or failed authentication.

  Parameters:

  • headers (required) — string — The raw email headers (the part above the message body).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• check_cold_email read-only

  Score a cold email (subject and body) out of 10 against the rules Pipefire checks its own emails with: length, reading level, the ask, subject line, and spam-filter wording. Returns each issue with why it matters and how to fix it.

  Parameters:

  • subject (required) — string
  • body (required) — string
  • kind — string — Which email in the sequence. Default first.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• test_subject_line read-only

  Score a cold email subject line out of 10: length, wording that hurts opens, and spam trigger words, with fixes.

  Parameters:

  • subject (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• suggest_sending_domains read-only

  Suggest lookalike sending domains for cold email (so the main domain is never put at risk), with live .com/.net availability. Give a business name or its website.

  Parameters:

  • brand (required) — string — Business name (Acme Roofing) or main domain (acmeroofing.com).

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• guess_email_addresses read-only

  List the likely email address formats for a person at a company domain (first@, first.last@, flast@ ...). Guesses only: verify before sending.

  Parameters:

  • first (required) — string
  • domain (required) — string
  • last — string
  • middle — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• generate_spf_record read-only

  Build a valid SPF TXT record for a domain from the email services it sends with, with warnings about the 10-lookup limit.

  Parameters:

  • a — boolean
  • mx — boolean
  • ip4 — array
  • ip6 — array
  • strict — boolean — true = -all (hard fail), false = ~all (soft fail, the safer default).
  • includes — array — Other include: domains, e.g. sendgrid.net, mailgun.org.
  • providers — array — Mailbox providers: google (Google Workspace), microsoft (Microsoft 365), zoho (Zoho Mail), zoho-eu (Zoho Mail (EU data center)).

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• generate_dmarc_record read-only

  Build a valid DMARC TXT record (to publish at _dmarc.yourdomain) from a policy and report addresses.

  Parameters:

  • domain (required) — string
  • policy (required) — string — Start with none plus a report address, then tighten.
  • rua — array — Aggregate report addresses.
  • subdomainPolicy — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• generate_dkim_record read-only

  Format a DKIM public key as the TXT record to publish at selector._domainkey.yourdomain.

  Parameters:

  • selector (required) — string
  • publicKey (required) — string — The public key, PEM or bare base64.
  • keyType — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.