Pipefire MCP server

• Registry nameai.pipefire/pipefireverified in the MCP registry

The registry name sits under pipefire.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools16
• Server calls itselfpipefire
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 258 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer563 ms
• Space in an agent's context≈ 2,102 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsA · 94 of 100
• Typed results0 of 16 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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…

• 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_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.

• 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_mx

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

• 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_mta_sts

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

• 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.

• 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_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.

• test_subject_line

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

• 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.

• 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.

• 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.

• generate_dmarc_record

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

• generate_dkim_record

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