Skip to content

MailAuth Audit (Email Deliverability)

Audits a domain's SPF, DKIM, DMARC and MX for spoofing risk and deliverability. $1.50/call via x402.

build.protocol_tooling.mcp

What our last check of MailAuth Audit (Email Deliverability) found

Stork connects to every MCP server it lists that has a public endpoint and records what came back: every week when the server answers without an account, every month otherwise. These are the results for MailAuth Audit (Email Deliverability).

Result
AnsweredThe endpoint completed an MCP handshake with no account.
Last checked
Tools listed
2
Context cost of the tool definitions
About 595 tokensWhat MailAuth Audit (Email Deliverability) adds to a model's context before you ask anything, unless your client loads tools on demand. Estimated from the length of the definitions at 4 characters a token.
Test call
Tool asked for a keyOn 17 November 2026 we called one read-only tool, audit_mailauth, once with a plain test input. MailAuth Audit (Email Deliverability) lists its tools without an account, but this tool would not run without a key or account from the publisher.

Changes to the tool definitions

We have seen no change to MailAuth Audit (Email Deliverability)'s tool definitions since we began checking it.

A check is one initialize request and one tools/list request from Stork's servers, with no account. Where a server answers without an account we also call one read-only tool once. Neither can tell you that every tool does its job or that the server is safe to connect.

Install MailAuth Audit (Email Deliverability) in your MCP client

MailAuth Audit (Email Deliverability) is a Model Context Protocol server. Add it to your MCP client config once, restart, and the server's tools become available to your AI assistant. The same JSON snippet below works across all four major clients — only the config file path differs.

  1. Locate your client's MCP config file.
    • Cursor: ~/.cursor/mcp.json
    • Claude Desktop (macOS): ~/Library/Application Support/Claude/claude_desktop_config.json
    • Claude Desktop (Windows): %APPDATA%\Claude\claude_desktop_config.json
    • VS Code: Settings → Extensions → MCP
    • Windsurf: Settings → MCP Servers
  2. Add MailAuth Audit (Email Deliverability) to the mcpServers map — paste the snippet below into your config file. If you already have other MCP servers, merge the entry into the existing mcpServers object.
  3. Restart your client so it picks up the new server.
  4. Verify — ask the assistant to list available tools; MailAuth Audit (Email Deliverability)'s tools should appear.
{
  "mcpServers": {
    "mailauth-audit--email-deliverability-": {
      "url": "https://mailauth-al6bxcngia-ue.a.run.app/mcp"
    }
  }
}

Maintain MailAuth Audit (Email Deliverability), or spotted a wrong detail on this page? Report a problem and we will correct it. Corrections are free.

Install MailAuth Audit (Email Deliverability) in Cursor

Open ~/.cursor/mcp.json in your editor, paste the snippet above into mcpServers, save, and restart Cursor. MailAuth Audit (Email Deliverability) will show up in the assistant's tool list on next launch.

Install MailAuth Audit (Email Deliverability) in Claude Desktop (macOS)

Open ~/Library/Application Support/Claude/claude_desktop_config.json in your editor, paste the snippet above into mcpServers, save, and restart Claude Desktop (macOS). MailAuth Audit (Email Deliverability) will show up in the assistant's tool list on next launch.

Install MailAuth Audit (Email Deliverability) in Claude Desktop (Windows)

Open %APPDATA%\Claude\claude_desktop_config.json in your editor, paste the snippet above into mcpServers, save, and restart Claude Desktop (Windows). MailAuth Audit (Email Deliverability) will show up in the assistant's tool list on next launch.

Install MailAuth Audit (Email Deliverability) in VS Code

Open Settings → Extensions → MCP in your editor, paste the snippet above into mcpServers, save, and restart VS Code. MailAuth Audit (Email Deliverability) will show up in the assistant's tool list on next launch.

Tools exposed by MailAuth Audit (Email Deliverability)

Once installed, MailAuth Audit (Email Deliverability) exposes the following MCP tools to your AI assistant. Each tool can be called directly by the assistant whenever its capability is relevant to your prompt.

  • audit_mailauth

    Full email deliverability audit of a domain (bare domain, e.g. example.com). Resolves the domain's mail DNS over DNS-over-HTTPS and runs 12 weighted checks: MX presence and redundancy, SPF presence, validity (single record, <=10 DNS lookups), and terminal policy (-all vs ~all vs ?all), DMARC presenc

  • audit_mailauth_lite

    FREE lite email deliverability audit of a domain (bare domain, e.g. example.com). Runs the same 12 SPF/DKIM/DMARC/MX checks as audit_mailauth but returns top-line results only: 0-100 score, A-F grade, spoofing/deliverability risk level, check counts, and the titles of the top gaps — the observed rec

Transport

MailAuth Audit (Email Deliverability) supports the following MCP transports. Most AI clients use stdio by default for locally-installed servers.

streamable-http

Other Model Context Protocol servers in the same space as MailAuth Audit (Email Deliverability). Each one adds different capabilities to your AI assistant — pick based on the data sources or workflows you need.

Browse the full MCP server directory or use Stork's one-line install to let your agent pick the right server automatically.