Home / MCP registry index / io.github.dmarc-examiner/mcp
io.github.dmarc-examiner/mcp
io.github.dmarc-examiner/mcp in the official MCP registry.
Endpoint https://mcp.dmarc-examiner.com/mcp. Source: github.com/dmarc-examiner/mcp.
The registry describes it as: Read your own DMARC aggregate and forensic reports: sources, alignment, alerts, CSV export.
We read its 21 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
list_domains get_domain check_dmarc create_domain verify_domain delete_domain list_reports get_report get_report_statistics export_report_csv list_alerts dismiss_alert list_forensic_reports get_forensic_report get_forensic_reports_statistics get_forensic_reports_summary list_webhooks create_webhook update_webhook delete_webhook test_webhook
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-dmarc-examiner-mcp)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.