Dmarc Examiner

io.github.dmarc-examinerPublished by GitHub account dmarc-examinerv1.1.0Updated Nov 2, 2026

Read your own DMARC aggregate and forensic reports: sources, alignment, alerts, CSV export.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Official DMARC Examiner MCP server that lets an assistant query your DMARC aggregate and forensic reports, domains, alerts and webhooks.

What you can do
  • List, inspect, add, verify and remove monitored domains, and check any domain's public DMARC record
  • List and read aggregate (RUA) reports, view statistics by country and ASN, and export reports as CSV
  • List and read forensic (RUF) reports, their statistics and a 7-day summary
  • List and dismiss security alerts
  • List, create, update, delete and test HTTPS webhook endpoints
When to use it
Useful when you already monitor domains with DMARC Examiner and want to ask questions about sending sources, SPF/DKIM alignment, alerts or forensic failures in an AI client instead of opening the dashboard or parsing XML reports.
Requirements
A DMARC Examiner account (a free tier is enough for basic use; forensic reports and webhooks need Pro or above). Connect to the remote endpoint at mcp.dmarc-examiner.com, or run the npm package with npx for clients without remote HTTP support. OAuth authorization in a browser is required on the first data call; the npx package stores tokens locally. The optional DMARC_EXAMINER_MCP_URL variable overrides the endpoint.
Before you install
The server can change data: it adds, verifies and soft-deletes domains, dismisses alerts, and creates, updates, deletes and tests webhooks, so grant only the scopes you need. The npx package stores OAuth tokens, including a refresh token, in a local credentials file. Forensic reports include raw failed message envelopes, which may contain sensitive email metadata. Some tools return 402 or 403 depending on your plan.

Installation

In SourceWeft

  1. Open Dmarc Examiner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.dmarc-examiner%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

@dmarc-examiner/mcp

[MCP] [License: MIT] [Tools]

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:

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

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

json
{  "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):

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

Claude Code

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

Cursor

Add to your Cursor MCP settings:

json
{  "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:

bash
npx -y @dmarc-examiner/mcp login    # authorize now, outside your MCP clientnpx -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

ToolDescriptionScope
list_domainsList all monitored domains in your organizationdomains:read
get_domainGet details of a specific domaindomains:read
check_dmarcInspect the public DMARC record at _dmarc.<domain>. Works on any domain, not only your owndomains:read
create_domainAdd a domain. Returns the reporting email and DMARC record to publish in DNSdomains:manage
verify_domainRe-check DNS to confirm the DMARC record carries your reporting addressdomains:manage
delete_domainRemove a domain from monitoring. Soft delete — historical reports remaindomains:manage

Aggregate reports (RUA)

ToolDescriptionScope
list_reportsList DMARC reports with filteringreports:read
get_reportGet a detailed report with recordsreports:read
get_report_statisticsReport statistics by country and ASNreports:read
export_report_csvExport a report as CSVreports:export

Forensic reports (RUF)

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

ToolDescriptionScope
list_forensic_reportsList RUF reports with filtering and paginationforensic:read
get_forensic_reportFull detail of a forensic report, including the failed message envelopeforensic:read
get_forensic_reports_statisticsCounters by failure type, delivery result, source IP with geolocation, and domainforensic:read
get_forensic_reports_summaryForensic activity over the last 7 daysforensic:read

Alerts

ToolDescriptionScope
list_alertsList security alertsalerts:read
dismiss_alertDismiss an alertalerts:manage

Webhooks

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

ToolDescriptionScope
list_webhooksList configured webhook endpointswebhooks:read
create_webhookCreate an endpoint. The URL must be HTTPSwebhooks:manage
update_webhookUpdate the URL, name or active state of an endpointwebhooks:manage
delete_webhookDelete an endpoint permanentlywebhooks:manage
test_webhookSend a webhook.test event and return the delivery statuswebhooks:manage

Scopes

ScopeDescription
domains:readView monitored domains
domains:manageAdd, verify and remove domains
reports:readView reports and statistics
reports:exportExport reports to CSV
forensic:readView forensic (RUF) reports
alerts:readView alerts
alerts:manageManage alerts (dismiss)
webhooks:readView webhook endpoints
webhooks:manageCreate, update, delete and test webhooks

Documentation

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

Support

License

MIT — see LICENSE.

Source: README.md at commit 6da6a70

Tools

21

list_domains

List all monitored domains in your organization

Parameterspageper_page

get_domain

Get details of a specific domain

Parametersdomain_idrequired

check_dmarc

Inspect the public DMARC record at _dmarc.<domain>. The domain does not need to belong to your organization. Returns parsed policy and rua/ruf addresses.

Parametersdomainrequired

create_domain

Add a new domain to the organization. Response includes the reporting_email and dmarc_record values to publish in DNS. May return 402 if the plan domain limit has been reached.

Parametersnamerequired

verify_domain

Re-check a domain's DNS to confirm the DMARC record contains the organization's reporting email. Updates status to verified on success.

Parametersdomain_idrequired

delete_domain

Remove a domain from monitoring. Soft-deletes; historical reports remain accessible.

Parametersdomain_idrequired

list_reports

List DMARC reports for your organization

Parameterspagedomaindate_toper_pagedate_from

get_report

Get details of a specific DMARC report

Parametersreport_idrequired

get_report_statistics

Get statistics for a specific DMARC report

Parametersreport_idrequired

export_report_csv

Export a DMARC report as CSV

Parametersreport_idrequired

list_alerts

List alerts for your organization

Parameterspagestatusper_page

dismiss_alert

Dismiss a specific alert

Parametersalert_idrequired

list_forensic_reports

List DMARC RUF (forensic) reports with optional filtering and pagination. Returns 403 if the plan does not include forensic reports (Pro plan and above).

Parameterspagedate_toper_pagedate_fromdomain_id

get_forensic_report

Get the full detail of a forensic (RUF) report by UUID, including the raw failed message envelope.

Parametersreport_idrequired

get_forensic_reports_statistics

Aggregated forensic-report counters grouped by auth failure type, delivery result, source IP (with geolocation) and reported domain.

Takes no parameters.

get_forensic_reports_summary

Summary of forensic activity in the last 7 days — useful for daily digest views.

Takes no parameters.

list_webhooks

List webhook endpoints configured for the organization. Returns 403 if the plan does not include advanced alerting (Pro and above).

Takes no parameters.

create_webhook

Create a new webhook endpoint. URL must start with https://. Returns 422 if the organization has reached its webhook limit.

Parametersurlrequirednamerequired

update_webhook

Update a webhook. Any combination of url, name and is_active may be provided; URL must remain HTTPS.

Parametersurlnameis_activewebhook_idrequired

delete_webhook

Delete a webhook endpoint permanently.

Parameterswebhook_idrequired

test_webhook

Send a synchronous webhook.test event to verify connectivity. Returns the delivery status. Test events do NOT update last_triggered_at, last_status or failure_count.

Parameterswebhook_idrequired

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts