Dmarc Examiner MCP server
online · 100% uptimeio.github.dmarc-examiner/mcp·v1.1.0Read your own DMARC aggregate and forensic reports: sources, alignment, alerts, CSV export.
0 stars29 downloads/wk
Reviews
Write oneNobody has reviewed Dmarc Examiner yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Dmarc Examiner tools (21, 6 write)
write = sends, deletes, buys or postscheck_dmarcFreeInspect the public DMARC record at _dmarc.<domain>. The domain does not need to belong to your organization. Returns parsed policy and rua/ruf addresses.
create_domainwrite actionFreeAdd 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.
create_webhookwrite actionFreeCreate a new webhook endpoint. URL must start with https://. Returns 422 if the organization has reached its webhook limit.
delete_domainwrite actionFreeRemove a domain from monitoring. Soft-deletes; historical reports remain accessible.
delete_webhookwrite actionFreeDelete a webhook endpoint permanently.
dismiss_alertFreeDismiss a specific alert
export_report_csvFreeExport a DMARC report as CSV
get_domainFreeGet details of a specific domain
get_forensic_reportFreeGet the full detail of a forensic (RUF) report by UUID, including the raw failed message envelope.
get_forensic_reports_statisticsFreeAggregated forensic-report counters grouped by auth failure type, delivery result, source IP (with geolocation) and reported domain.
get_forensic_reports_summaryFreeSummary of forensic activity in the last 7 days — useful for daily digest views.
get_reportFreeGet details of a specific DMARC report
get_report_statisticsFreeGet statistics for a specific DMARC report
list_alertsFreeList alerts for your organization
list_domainsFreeList all monitored domains in your organization
list_forensic_reportsFreeList DMARC RUF (forensic) reports with optional filtering and pagination. Returns 403 if the plan does not include forensic reports (Pro plan and above).
list_reportsFreeList DMARC reports for your organization
list_webhooksFreeList webhook endpoints configured for the organization. Returns 403 if the plan does not include advanced alerting (Pro and above).
test_webhookwrite actionFreeSend 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.
update_webhookwrite actionFreeUpdate a webhook. Any combination of url, name and is_active may be provided; URL must remain HTTPS.
verify_domainFreeRe-check a domain's DNS to confirm the DMARC record contains the organization's reporting email. Updates status to verified on success.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- Live reliabilityremote reachable in 1673ms20/20
- Tool poisoning21 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 6 write-action tools with no auth3/15
- Maintenancelast push 36 days ago12/15
- Maintainer identityregistry namespace matches repository owner7/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How Dmarc Examiner compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 63% of 48,255 servers
- Tools
- 21
- the typical server has 7
- Tools that change things
- 29%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 575 ms
- faster than 25% of 30,031 servers
- Downloads a week
- 29
- more than 16% of 12,191 servers with a package
What its tools let an agent do: 15 read · 2 create · 2 change · 2 delete
Install Dmarc Examiner in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp https://mcp.dmarc-examiner.com/mcp
What the publisher says
From the Dmarc Examiner repository's README, as published. We do not edit it. Read it on GitHub
@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/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.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/mcpCursor
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:
- Log in to your DMARC Examiner account
- Select which organization to connect
- 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 credentialsSet DMARCEXAMINERMCP_URL to point the package at a different endpoint.
Available Tools
Domains
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Dmarc Examiner: common questions
- Is Dmarc Examiner MCP server safe?
- Mostly: it is graded B (82/100). Read the Dmarc Examiner safety report
- How do I install Dmarc Examiner?
- It runs remotely at mcp.dmarc-examiner.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Dmarc Examiner need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is Dmarc Examiner maintained?
- The last commit was 77 days ago (2026-08-19). The latest release is v1.1.0.
- Is Dmarc Examiner up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Dmarc Examiner compare with other MCP servers?
- safety score 82/100 (higher than 63% of 48,255 servers); tools 21 (the typical server has 7); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.