analyze_dmarc_report — TamingDNS MCP Tool
analyze_dmarc_report
(analyze dmarc report) is one of 19 tools on the
TamingDNS
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_dmarc_report from your client
- Claude Code TamingDNS analyze_dmarc_report run in your project directory
- Claude Desktop TamingDNS analyze_dmarc_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TamingDNS analyze_dmarc_report ~/.cursor/mcp.json
- VS Code TamingDNS analyze_dmarc_report .vscode/mcp.json
- Zed TamingDNS analyze_dmarc_report ~/.config/zed/settings.json
- Windsurf TamingDNS analyze_dmarc_report ~/.codeium/windsurf/mcp_config.json
- Cline TamingDNS analyze_dmarc_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TamingDNS analyze_dmarc_report ~/.gemini/settings.json
- Grok TamingDNS analyze_dmarc_report .mcp.json (in your project root)
- ChatGPT TamingDNS analyze_dmarc_report Settings → Connectors → Advanced → Developer mode
- Claude.ai TamingDNS analyze_dmarc_report Settings → Connectors → Add custom connector
- LangChain TamingDNS analyze_dmarc_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://tamingdns.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.