Dmarc Examiner MCP

@dmarc-examiner/mcp

Official MCP (Model Context Protocol) server for DMARC Examiner. Query your DMARC monitoring data from AI assistants like Claude Desktop, Claude Code, and Cursor.

Why

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.

Quick Setup

Option 1: Remote URL (Recommended)

Most MCP clients support remote HTTP servers directly. Add this to your MCP configuration:

{

"mcpServers": { "dmarc-examiner": { "url": "https://mcp.dmarc-examiner.com/mcp" } } }

Option 2: npx (for clients without remote HTTP support)

{

"mcpServers": { "dmarc-examiner": { "command": "npx", "args": ["-y", "@dmarc-examiner/mcp"] } } }

Configuration by Client

Claude Desktop

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 Code

claude mcp add dmarc-examiner --transport http https://mcp.dmarc-examiner.com/mcp

Cursor

Add to your Cursor MCP settings:

{

"mcpServers": { "dmarc-examiner": { "url": "https://mcp.dmarc-examiner.com/mcp" } } }

Authorization

Adding the server does not require authorizing. It starts immediately and answers initialize, tools/list and ping without credentials, so your client can list all 21 tools straight away.

A browser opens the first time you call a tool that touches your data. You'll need to:

1. Log in to your DMARC Examiner account
2. Select which organization to connect
3. Approve the requested permissions (scopes)

The call you made is then replayed automatically, so it completes rather than failing.

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.

Why it works this way. Authorizing on startup is the obvious design and it breaks every automated client: directory checks, scanners and CI have no browser to open, so the server appears to hang and the check times out. We wrote up the failure and the fix, with logs, in Your Remote MCP Server Will Fail Every Directory Check.

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 credentials

Set DMARC_EXAMINER_MCP_URL to point the package at a different endpoint.

Available Tools

Domains

Aggregate reports (RUA)

Forensic reports (RUF)

Requires the Pro plan or above; these return 403 otherwise.

Alerts

Webhooks

Requires the Pro plan or above; these return 403 otherwise.

Scopes

Documentation

For detailed documentation, visit: https://dmarc-examiner.com/docs/settings/mcp-integration?utm_source=github&utm_medium=content&utm_campaign=mcp-repo

Support

• Documentation: https://dmarc-examiner.com/docs?utm_source=github&utm_medium=content&utm_campaign=mcp-repo
• Email: support@dmarc-examiner.com

License

MIT — see LICENSE.