PowerDMARC MCP
https://mcp.powerdmarc.com/sse ↗
Description
PowerDMARC brings your email-authentication data into any AI assistant. Check domain health, analyze DMARC aggregate reports (by country, sending source, result, and more), look up live DNS and WHOIS records, and generate correctly-formatted DMARC, SPF, and DKIM records — all in natural language. Ask how secure a domain is and get an interpreted DMARC, SPF, DKIM, BIMI, and MTA-STS breakdown. Dig into reports to see who's sending email as your domain and which sources are failing authentication. Authentication is handled securely via OAuth — the server accesses only what your PowerDMARC account already permits, and never stores your credentials or tokens.
What our measurements say
PowerDMARC MCP is a remote MCP server published at mcp.powerdmarc.com. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 335 ms, placing it among the faster endpoints. It exposes a broad tool surface of 30 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are specific to DMARC, SPF, DKIM, and DNS tasks.
- Coverage includes domain health, forensic data, and audit logs.
- Some tools explicitly define allowed parameters (e.g., DNS record types).
Weaknesses
- Tool names like 'domain_analyzer' are vague compared to more specific counterparts.
- Descriptions focus on functionality rather than use cases or triggers.
- Error handling, constraints, and parameter types are inconsistently documented.
- Potential overlap between 'domain_health' and 'domain_analyzer' may confuse agents.
domain_analyzer— Name lacks specificity compared to 'dmarc_aggregate_per_country'dns_lookup— Parameter constraints listed but no error handling for invalid inputsdomain_health— May overlap with 'domain_analyzer' in domain status checks
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from auth-gated to legacy · system transitioned to legacy mode, enabling new compliance checks
- 2026-09-11T03:50:39.090Z — complianceScore increased from null to 80, smokeOk changed from null to false · initial compliance score achieved but smoke test failed
- 2026-09-11T05:44:28.819Z — complianceScore increased from 80 to 100, smokeOk changed from false to null · compliance reached maximum score, smoke test status reset
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test failed · last run:
- Cold-start: cold 258ms → warm 213ms (penalty 45ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.0.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/powerdmarcmcp-dmarcmcp)<a href="https://mcpmetrics.io/servers/powerdmarcmcp-dmarcmcp"><img src="https://mcpmetrics.io/badge/powerdmarcmcp/dmarcmcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see