DMARC & DNS MCP Server
DMARC MCP Server and DNS MCP Server provide programmatic access to DMARC analytics, DNS records, and domain monitoring through the Model Context Protocol (MCP). Connect your development tools to access email authentication data programmatically.
Start with a 1-week free trial to test it out
Key Features
The DMARC MCP Server and DNS MCP Server provide comprehensive programmatic access to email authentication data and DNS records through Model Context Protocol endpoints.
Installation Guide
Connect the DMARC MCP Server or DNS MCP Server to MCP-compatible tools and start accessing DMARC and DNS data programmatically.
Sign up below to get started. Full installation instructions are available after signup at
app.dmarcdkim.com/mcp-instructions
Test for free
Start with a 1-week free trial
Step 1: Create an API Key with MCP Scope
After signing up, create an API key with MCP scope to authenticate your MCP server connection.
Create an API key with MCP scope from your account settings
Step 2: Connect to MCP Clients
Use your API key to connect the DMARC MCP Server to your preferred development tool. We support Claude Code, Cursor (1-click install), VS Code, and other MCP-compatible clients.
Full installation instructions are available after signup at
app.dmarcdkim.com/mcp-instructions
Talk to DMARC Reports via MCP
We're working on bringing DMARC report data directly to your MCP server. Get notified when this feature becomes available.
Access your DMARC aggregate reports programmatically through the Model Context Protocol. This feature will allow you to query report data, analyze email authentication results, and integrate DMARC insights into your development workflow.
MCP Tools & Use Cases
The DMARC MCP Server provides four powerful tools for DNS and email authentication analysis. Learn how each tool works and when to use them.
DNS Lookup Tool
Performs comprehensive DNS lookups for domains and IP addresses with support for all standard and email authentication record types.
Supported Lookup Types:
- Standard records: A, AAAA, MX, TXT, NS, CNAME
- Email authentication: SPF, DMARC
- Reverse DNS: PTR lookups
- Domain information: WHOIS data
- Bulk queries: "all" type for multiple records
Use Cases:
- Verify DNS record configuration
- Check email server MX records
- Retrieve SPF and DMARC email authentication records
- Perform reverse DNS lookups for IP addresses
- Retrieve domain WHOIS information
Example:
Use the DmarcDkim MCP server to check DNS records for example.com. Retrieve A records for IP addresses, MX records for email servers, and SPF and DMARC records for email authentication.
Retrieved A records (192.0.2.1, 192.0.2.2), MX records (mail.example.com priority 10), SPF record (v=spf1 include:_spf.google.com ~all), DMARC record (v=DMARC1; p=none; rua=mailto:dmarc@example.com). All email authentication records retrieved successfully.
DMARC Check Tool
Validates DMARC policy records and SPF records for a domain with comprehensive error detection and reporting. This tool checks the _dmarc subdomain for DMARC policies and validates SPF record configuration.
What It Checks:
- DMARC policy records from _dmarc subdomain
- SPF records (TXT records starting with v=spf1)
- DMARC configuration errors and syntax issues
- DNS record availability and validity
Use Cases:
- Verify email authentication DNS setup for a domain
- Diagnose email delivery issues related to authentication
- Check if domain is properly configured for DMARC
- Verify SPF records are present and correctly formatted
- Get a quick overview of DMARC and SPF status
Example:
Use the DmarcDkim MCP server to check DMARC and SPF records for example.com. Verify the email authentication configuration and report any errors or policy issues.
DMARC policy found (v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com), SPF record present (v=spf1 include:_spf.google.com ~all). No configuration errors detected. The domain is properly configured for DMARC enforcement.
SPF Check Tool
Validates SPF record syntax, checks DNS lookup count against RFC 7208 limits, and detects circular references.
Validation Features:
- Syntax validation and error detection
- DNS lookup count (RFC 7208 limit: 10 lookups)
- Circular reference detection in include/redirect chains
- SPF tree structure parsing with all mechanisms
Use Cases:
- Validate SPF record before deployment
- Ensure compliance with RFC 7208 (10 lookup limit)
- Detect configuration errors that could break email delivery
- Understand SPF record structure and mechanisms
Example:
Use the DmarcDkim MCP server to validate the SPF record for example.com. Check for syntax errors, verify DNS lookup count is ≤10 (RFC 7208 limit), and detect any circular references in include chains.
SPF record found: v=spf1 include:_spf.google.com include:_spf.salesforce.com include:_spf.mailchimp.com ~all. Validation results: 12 DNS lookups required (exceeds RFC 7208 limit of 10 - this will cause email delivery failures). Syntax error detected in include statement: invalid domain format in "include:_spf.mailchimp.com". Circular reference detected in include chain: example.com → other.com → example.com. The SPF tree structure shows the problematic include chain that needs optimization.
SPF Merge Tool
Merges multiple SPF records or mechanisms into a single optimized record with duplicate removal and proper formatting.
Features:
- Removes duplicate mechanisms
- Sorts mechanisms by type and qualifier
- Preserves qualifiers (-, ~, +, ?)
- Adds recommended "~all" if missing
- Handles modifiers (redirect, exp)
Use Cases:
- Consolidate multiple SPF records into one
- Merge SPF records when migrating email providers
- Optimize SPF records by removing duplicates
- Combine existing domain SPF with new mechanisms
Example:
Use the DmarcDkim MCP server to merge SPF records. Fetch the existing SPF record from example.com and combine it with ip4:192.168.1.0/24 and include:_spf.newprovider.com. Remove duplicates and create a single optimized record ready for deployment.
Successfully merged SPF records. Original domain SPF: v=spf1 include:_spf.google.com ~all. New mechanisms added: ip4:192.168.1.0/24, include:_spf.newprovider.com. Merged result: v=spf1 include:_spf.google.com include:_spf.newprovider.com ip4:192.168.1.0/24 ~all. Duplicates removed, mechanisms sorted by type, qualifiers preserved, ready for deployment. Note: After deployment, validate the merged record with SPF Check to ensure it complies with RFC 7208 limits.
Tips for Using MCP Tools
Connect Your Domain
Connect your domain to start using the DMARC MCP Server and DNS MCP Server. Access DMARC analytics, DNS records, and domain monitoring through Model Context Protocol endpoints.
MCP access is available in Pro and Hassle-free plans
DMARC MCP Server Questions & Answers
The DMARC MCP Server is a Model Context Protocol (MCP) server that provides programmatic access to DNS records and email authentication DNS configurations. This MCP server enables applications and tools to query DNS records, check DMARC policy records, validate SPF configurations, and perform comprehensive DNS lookups through standardized MCP endpoints. Whether you're building integrations with development tools like Claude Code, Cursor, or VS Code, the DMARC MCP Server offers seamless access to DNS and email authentication record checking.
DNS MCP Server is a component of the DMARC MCP Server that provides comprehensive DNS record access. This MCP server enables applications to query DNS records including A, AAAA, MX, TXT, NS, CNAME, PTR, and WHOIS records. It also provides specialized lookups for email authentication records including SPF records and DMARC policy records. The DNS MCP Server offers programmatic DNS record access through Model Context Protocol endpoints.
Model Context Protocol (MCP) is a standardized protocol that enables applications to access contextual data through server endpoints. The DMARC MCP Server and DNS MCP Server implement the MCP protocol to provide programmatic access to DNS records, SPF configurations, DKIM settings, and DMARC policy records. Applications can query these MCP servers using standardized endpoints to retrieve DNS information and validate email authentication configurations.
The DMARC MCP Server provides four powerful tools: (1) DNS Lookup - comprehensive DNS lookups for all record types including email authentication records (SPF, DMARC), (2) DMARC Check - validates DMARC and SPF DNS records for domains with error detection, (3) SPF Check - validates SPF record syntax, checks DNS lookup count against RFC 7208 limits, and detects circular references, and (4) SPF Merge - merges multiple SPF records into a single optimized record. You can integrate the DMARC MCP Server with development tools like Claude Code, Cursor, VS Code, and other MCP-compatible applications.
You can connect to the DMARC MCP Server and DNS MCP Server by configuring your MCP-compatible tool with the appropriate server endpoints. The installation process varies by tool - for Claude Code, you can use the CLI command or manually edit the configuration file. For Cursor, use the 1-click install button. For VS Code and other clients, follow the installation guides provided on this page. After signup, full installation instructions are available at app.dmarcdkim.com/mcp-instructions.
MCP server DNS refers to using a Model Context Protocol (MCP) server to access DNS records programmatically. The DNS MCP Server component provides MCP server DNS functionality, enabling applications to query DNS records, SPF configurations, and DMARC policy records through MCP endpoints. This MCP server DNS solution offers a standardized way to access DNS data programmatically for email authentication validation and DNS record checking.
The DMARC MCP Server provides tools to check DMARC DNS policy records and validate SPF configurations. It enables you to programmatically verify email authentication DNS configurations for domains. However, actual DMARC report data and analytics are available through the web dashboard at app.dmarcdkim.com. The MCP server focuses on DNS record checking and validation rather than report analytics.