DNS + email auth, MCP native

Email authentication your AI operator can actually run.

Authwright helps MSPs and agencies coordinate SPF, DMARC, DKIM DNS publication and MTA-STS on supported providers. Review the inputs, write only when authorized, and verify the result.

Public check, no signupDMARC / SPF / DKIM / MTA-STS / MX

GODADDY / NAMECHEAP / CLOUDFLARE / PORKBUN / ROUTE 53

One workflow across the registrar mix agencies already inherited.

Illustrative DNS review for

example.com

C+

64/100

SPFwarn9 top-level SPF terms
DKIMfailcommon selector not found
DMARCwarnmonitoring policy: p=none
MTA-STSfailpolicy host not found

Proposed changeset

+ TXT _dmarc "v=DMARC1; p=quarantine; rua=..."

- stale SPF include:spf.oldvendor.example

+ CNAME mta-sts - authwright managed policy host

Claude Code / MCPauthwright
> Propose email-auth changes for example.com.
Illustrative workflow, not a live result:
email_auth_diagnose → email_auth_propose
Supply known senders; skipBimi: true.
Review the changeset before email_auth_apply.
DKIM signing must be enabled at the mail provider.

Sender requirements

Authentication is necessary. Delivery still takes more.

Gmail requires SPF or DKIM for all senders to personal Gmail accounts. Senders around 5,000 messages per day need both, plus DMARC and alignment. Yahoo also has stricter requirements for bulk senders. A monitoring DMARC policy can meet the authentication minimum; it is not enforcement.

Reputation, complaint rates, unsubscribe handling and message practices also matter. Check the current Gmail sender guidelines and Yahoo requirements for your sender category.

Inventory legitimate senders before tightening policy. Follow the MSP email-auth rollout checklist.

Email EasyPass

A coordinated workflow, with explicit inputs.

Email EasyPass is Authwright's email-authentication workflow. Under the hood it's the email_auth_wizard MCP tool. Supply an authorized domain, supported provider, sender inputs and policy choices. The wizard can write; use separate proposal and apply calls when you need a review step. Pro or above is required.

  1. 01Reads

    Published SPF, common DKIM selectors, DMARC, MTA-STS and BIMI signals. Not a sent-message or inbox-placement test.

  2. 02Proposes

    Changes using your sender inventory and policy choices. Review before calling write-capable tools.

  3. 03Writes

    Authorized DNS changes on supported providers. DKIM records must come from your mail provider, which also enables signing.

  4. 04Hosts

    Managed MTA-STS HTTPS policy hosting via Azure Front Door, after DNS validation and certificate provisioning.

  5. 05Checks

    Observed propagation for requested changes. A timeout or partial result still needs operator follow-up.

  6. 06Reports

    Query collected DMARC aggregate reports when a reporting destination and ingestion are configured.

Keep mail-provider signing and BIMI logo/certificate preparation separate. Read the MTA-STS setup guide before enforcing transport policy.

MCP, not SaaS

If your team lives in Claude, Cursor, or ChatGPT, this is the tool your stack was missing.

Authwright is built as a Model Context Protocol server — which means it's callable directly from the AI environments your operators already use.

Use the portal to create a workspace, prove domain control and connect a provider. Then configure your MCP client for authorized DNS operations.

Read and propose before applying changes. Tool authorization does not replace an operator reviewing sender inputs, provider limits and recovery steps.

Claude CodeIllustrative example
> Diagnose email authentication for example.com.
1. email_auth_diagnose: inspect published DNS signals
2. email_auth_propose: supply sender inputs; skipBimi: true
3. Operator reviews the proposed record changes
4. email_auth_apply: authorized write (Pro+)
5. wait_for_propagation: inspect observed results

DKIM signing stays with the mail provider.

What makes it different

Tools for a deliberate rollout.

  • LLM-callable, not click-callable.

    Native MCP server. Works in Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP-compatible client. No dashboard tax.

  • We host your MTA-STS policy.

    Pro and above includes managed HTTPS policy hosting through Azure Front Door. DNS validation and certificate readiness are part of setup, not instant guarantees.

  • SPF flattening for the 10-lookup limit.

    SPF limits lookup-causing terms during evaluation, including nested includes. Inspect a flattening candidate and its warnings before writing; address resolution and ongoing refresh need separate review.

  • Five providers, explicit support limits.

    GoDaddy, Namecheap, Cloudflare, Porkbun and Route 53 share a tool vocabulary. Credentials, supported operations, account permissions and plan limits still differ.

Beyond email auth

Beyond DMARC: tools for everyday domain operations.

Once Authwright is in your MCP session, use selected tools across DNS, SSL, domain registration, bulk operations, and health diagnostics. Provider support, credentials and tier gates still apply.

  • Bulk DNS at portfolio scale

    Team+ batch tools operate on selected domains. Review a preview explicitly, retain a recovery plan and inspect individual failures.

    bulk_update_dns · dns_changeset_preview · replace_dns_records

  • SSL certificate lifecycle

    Inspect certificates and supported lifecycle actions. Renew/reissue are GoDaddy-specific here; other providers have different limits.

    check_certificate_expiry · renew_certificate · reissue_certificate

  • Defensive registration at scale

    On supported providers, check domain availability and review purchases deliberately. Registration can incur provider charges.

    get_domain_suggestions · bulk_check_availability · purchase_domain

  • DNSSEC without the dashboard slog

    Read or change DNSSEC where the adapter supports it. Namecheap toggles are unsupported; Route 53 needs existing KSK and delegation prerequisites.

    enable_dnssec · get_dnssec · disable_dnssec

Self-service setup

Create the workspace, prove the domain, connect keys, then install MCP.

  1. 1Step 1

    Create a workspace.

    Sign in with Google, Microsoft, or a magic link. First login creates a free workspace automatically.

  2. 2Step 2

    Add and prove a domain.

    Save a domain, publish the one-time TXT proof, then verify ownership in the portal.

  3. 3Step 3

    Connect registrar keys.

    Paste GoDaddy API key and secret or a Cloudflare API token into the broker-owned ingest form.

  4. 4Step 4

    Generate MCP access.

    Issue a workspace-scoped bridge token for Claude Code, Cursor, Codex, or VS Code and start running governed DNS workflows.

Pricing

Priced for the way agencies actually work.

Per-agency pricing, not per-seat. Start with diagnosis. Pro adds email-auth writes, managed MTA-STS hosting, flattening and report access; Team adds bulk tools.

RECOMMENDED
Team$99 /mo
25 domains · 5 registrars
  • RBAC + SSO
  • Up to 10 seats
  • 30-day snapshots
Choose Team
Free$0 /mo
1 domain · 1 registrar
  • Public audit, unlimited
  • MCP server access
  • 7-day snapshots
Choose Free
Pro$29 /mo
5 domains · 1 registrar
  • Everything in Free
  • 30-day snapshots
  • Email + chat support
Choose Pro
Agency$299 /mo
100 domains · 15 registrars
  • Multi-tenant workspaces
  • Priority support
Choose Agency
Agency Plus$799 /mo
500 domains · unlimited
  • Dedicated success mgr
  • 99.95% SLA
Choose Agency Plus
EnterpriseTalk to us
500+ · unlimited
  • Custom contract
  • VPC peering
Contact sales

Five provider brands are supported: GoDaddy, Namecheap, Cloudflare, Porkbun and Route 53. Available operations depend on provider, account permissions and plan. Start free. Upgrade, downgrade, or cancel from the portal.

Talk to the founder →

Free public audit

Start with published email-auth DNS.

Drop any domain into our free checker. We'll show you the current DMARC policy, top-level SPF terms, common DKIM selectors, MTA-STS TXT and MX. The grade is a DNS heuristic, not a delivery guarantee. No login. No email gate. No upsell pop-up.

Run a free check →

FAQ

Questions MSPs actually ask.

Q1.Can I use Authwright with an existing DMARC reporting tool?
Yes. You can use MCP DNS workflows while retaining another reporting destination. Check reporting configuration and provider support before changing records.
Q2.What does an MCP server mean for my workflow?
Connect a compatible MCP client to your workspace. Read diagnosis and proposed changes, then call authorized write tools deliberately. The wizard does not promise a separate approval dialog.
Q3.Which DNS providers are supported?
GoDaddy, Namecheap, Cloudflare, Porkbun and Route 53. The authoritative DNS host matters, not just where you bought the domain. Operations and account eligibility differ.
Q4.Does a good DNS score guarantee delivery?
No. The public check is a DNS heuristic. It cannot verify actual message signing, alignment, sender reputation or inbox placement.
Q5.How does MTA-STS hosting work?
Pro and above provides managed HTTPS policy hosting through Azure Front Door. Complete DNS validation and certificate provisioning, confirm MX/TLS readiness, and test before enforcement. Cached policies mean rollback is not immediate everywhere.
Q6.Can I white-label this for my clients?
White-label is on the roadmap for Agency Plus and Enterprise. Contact founder@authwright.com with your requirements.
Q7.What about DKIM and BIMI?
Get the public DKIM record and enable signing at your mail provider. Authwright does not generate signing keys. BIMI needs a real logo and mailbox-provider certificate requirements; end-to-end BIMI validation is not implemented. Omit it from automated proposals until prepared.
Q8.Where do registrar credentials go?
Credential ingestion and use are broker-owned, with encrypted storage in Azure Key Vault. Scope provider credentials narrowly and review the security page. Do not paste private keys into prompts.
Q9.What is free, and what needs a paid plan?
The public DNS check needs no login. Pro adds email-auth apply, wizard, hosting, flattening and report access; Team adds bulk tools. Provider and domain limits still apply.
Q10.Who is behind Authwright?
Authwright is built by Milton Hubbard. Contact founder@authwright.com for product questions.

Start here

Create your workspace and connect a registrar.

There is no separate sales form. Sign in, land in a free workspace, add a domain, prove ownership, then connect registrar API keys from the portal. Upgrade only when you need more domains.