get_report — mcp MCP Tool Read-only
get_report
(get report) is one of 21 tools on the
mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_report from your client
- Claude Code mcp get_report run in your project directory
- Claude Desktop mcp get_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp get_report ~/.cursor/mcp.json
- VS Code mcp get_report .vscode/mcp.json
- Zed mcp get_report ~/.config/zed/settings.json
- Windsurf mcp get_report ~/.codeium/windsurf/mcp_config.json
- Cline mcp get_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp get_report ~/.gemini/settings.json
- Grok mcp get_report .mcp.json (in your project root)
- ChatGPT mcp get_report Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp get_report Settings → Connectors → Add custom connector
- LangChain mcp get_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.dmarc-examiner.com/mcpOther tools on this server
- list_domains
- get_domain
- check_dmarc
- create_domain
- verify_domain
- delete_domain
- list_reports
- 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
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.