Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@DMARC Examiner MCP summarize the latest DMARC report statistics for example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Official MCP (Model Context Protocol) server for DMARC Examiner. Query your DMARC monitoring data from AI assistants like Claude Desktop, Claude Code, and Cursor.
DMARC aggregate reports arrive as compressed XML, one file per receiver per day. Reading them means either opening a dashboard or parsing XML by hand.
This server puts that data behind an MCP connection, so you can ask questions instead:
Which sending sources failed DMARC alignment last week?
Show me the domains where SPF passes but DKIM does not.
Export the report for example.com as CSV.
DMARC Examiner is a DMARC monitoring service with a free tier — you need an account to use this server, but not a paid one.
Related MCP server: Vectra AI MCP Server
Most MCP clients support remote HTTP servers directly. Add this to your MCP configuration:
{
"mcpServers": {
"dmarc-examiner": {
"url": "https://mcp.dmarc-examiner.com/mcp"
}
}
}{
"mcpServers": {
"dmarc-examiner": {
"command": "npx",
"args": ["-y", "@dmarc-examiner/mcp"]
}
}
}Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"dmarc-examiner": {
"url": "https://mcp.dmarc-examiner.com/mcp"
}
}
}claude mcp add dmarc-examiner --transport http https://mcp.dmarc-examiner.com/mcpAdd to your Cursor MCP settings:
{
"mcpServers": {
"dmarc-examiner": {
"url": "https://mcp.dmarc-examiner.com/mcp"
}
}
}On first use a browser window opens so you can authorize access. You'll need to:
Log in to your DMARC Examiner account
Select which organization to connect
Approve the requested permissions (scopes)
With Option 1 the MCP client runs this flow itself. With Option 2 the package does it: it registers as an OAuth client, opens your browser, and stores the resulting tokens in ~/.dmarc-examiner/mcp-credentials.json with 0600 permissions. The refresh token is reused on later runs, so the browser step happens once.
You can also drive it directly:
npx -y @dmarc-examiner/mcp login # authorize now, outside your MCP client
npx -y @dmarc-examiner/mcp logout # forget the stored credentialsSet DMARC_EXAMINER_MCP_URL to point the package at a different endpoint.
Tool | Description | Scope |
| List all monitored domains in your organization |
|
| Get details of a specific domain |
|
| Inspect the public DMARC record at |
|
| Add a domain. Returns the reporting email and DMARC record to publish in DNS |
|
| Re-check DNS to confirm the DMARC record carries your reporting address |
|
| Remove a domain from monitoring. Soft delete — historical reports remain |
|
Tool | Description | Scope |
| List DMARC reports with filtering |
|
| Get a detailed report with records |
|
| Report statistics by country and ASN |
|
| Export a report as CSV |
|
Requires the Pro plan or above; these return 403 otherwise.
Tool | Description | Scope |
| List RUF reports with filtering and pagination |
|
| Full detail of a forensic report, including the failed message envelope |
|
| Counters by failure type, delivery result, source IP with geolocation, and domain |
|
| Forensic activity over the last 7 days |
|
Tool | Description | Scope |
| List security alerts |
|
| Dismiss an alert |
|
Requires the Pro plan or above; these return 403 otherwise.
Tool | Description | Scope |
| List configured webhook endpoints |
|
| Create an endpoint. The URL must be HTTPS |
|
| Update the URL, name or active state of an endpoint |
|
| Delete an endpoint permanently |
|
| Send a |
|
Scope | Description |
| View monitored domains |
| Add, verify and remove domains |
| View reports and statistics |
| Export reports to CSV |
| View forensic (RUF) reports |
| View alerts |
| Manage alerts (dismiss) |
| View webhook endpoints |
| Create, update, delete and test webhooks |
For detailed documentation, visit: https://dmarc-examiner.com/docs/settings/mcp-integration?utm_source=github&utm_medium=content&utm_campaign=mcp-repo
Documentation: https://dmarc-examiner.com/docs?utm_source=github&utm_medium=content&utm_campaign=mcp-repo
Email: support@dmarc-examiner.com
MIT — see LICENSE.
DMARC analytics and domain onboarding for AI assistants — health, SPF/DKIM, compliance, anomalies.
Monitor and manage email authentication (SPF, DKIM, DMARC, MTA-STS, BIMI) for your domains.
Buy & manage domains from any AI chat: availability, register, DNS, email forwarding, AI bot stats.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/dmarc-examiner/mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server