analyze_email_headers — TamingDNS MCP Tool
analyze_email_headers
(analyze email headers) is one of 10 tools on the
TamingDNS
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_email_headers from your client
- Claude Code TamingDNS analyze_email_headers run in your project directory
- Claude Desktop TamingDNS analyze_email_headers ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TamingDNS analyze_email_headers ~/.cursor/mcp.json
- VS Code TamingDNS analyze_email_headers .vscode/mcp.json
- Zed TamingDNS analyze_email_headers ~/.config/zed/settings.json
- Windsurf TamingDNS analyze_email_headers ~/.codeium/windsurf/mcp_config.json
- Cline TamingDNS analyze_email_headers ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TamingDNS analyze_email_headers ~/.gemini/settings.json
- Grok TamingDNS analyze_email_headers .mcp.json (in your project root)
- ChatGPT TamingDNS analyze_email_headers Settings → Connectors → Advanced → Developer mode
- Claude.ai TamingDNS analyze_email_headers Settings → Connectors → Add custom connector
- LangChain TamingDNS analyze_email_headers 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 6 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.