# Pipefire email deliverability tools

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

- name: ai.pipefire/pipefire
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 89/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/ai.pipefire%2Fpipefire
- tools: https://api.protogrid.dev/v1/servers/ai.pipefire%2Fpipefire/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "pipefire": {
      "type": "http",
      "url": "https://pipefire.ai/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-0d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 16 of 16 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 2,276 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 0 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 16, about 2,276 tokens to load them all
- tool set hash: 5ba3468e7f01a90c75c819b6a160d829
- badge: [![protogrid quality](https://protogrid.dev/badge/ai.pipefire/pipefire.svg)](https://protogrid.dev/servers/ai.pipefire/pipefire)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://pipefire.ai/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (16)

- `analyze_email_headers`: 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.
- `check_bimi`: Check a domain's BIMI record (logo in the inbox) and whether its DMARC policy is strict enough for BIMI to show.
- `check_blacklists`: 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.
- `check_cold_email`: 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.
- `check_dkim`: Look up a domain's DKIM public key, trying the selectors Google Workspace, Microsoft 365 and common senders use, plus one you name.
- `check_dmarc`: 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.
- `check_domain_email_setup`: 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.
- `check_mta_sts`: Check a domain's MTA-STS policy, which forces encrypted delivery of incoming mail.
- `check_mx`: List a domain's mail servers (MX records) and which provider handles its email.
- `check_spf`: 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.
- `generate_dkim_record`: Format a DKIM public key as the TXT record to publish at selector._domainkey.yourdomain.
- `generate_dmarc_record`: Build a valid DMARC TXT record (to publish at _dmarc.yourdomain) from a policy and report addresses.
- `generate_spf_record`: Build a valid SPF TXT record for a domain from the email services it sends with, with warnings about the 10-lookup limit.
- `guess_email_addresses`: List the likely email address formats for a person at a company domain (first@, first.last@, flast@ ...). Guesses only: verify before sending.
- `suggest_sending_domains`: 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.
- `test_subject_line`: Score a cold email subject line out of 10: length, wording that hurts opens, and spam trigger words, with fixes.