analyze_email_headers — MailVakt MCP Tool
analyze_email_headers
(analyze email headers) is one of 8 tools on the
MailVakt
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 MailVakt analyze_email_headers run in your project directory
- Claude Desktop MailVakt analyze_email_headers ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MailVakt analyze_email_headers ~/.cursor/mcp.json
- VS Code MailVakt analyze_email_headers .vscode/mcp.json
- Zed MailVakt analyze_email_headers ~/.config/zed/settings.json
- Windsurf MailVakt analyze_email_headers ~/.codeium/windsurf/mcp_config.json
- Cline MailVakt analyze_email_headers ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MailVakt analyze_email_headers ~/.gemini/settings.json
- Grok MailVakt analyze_email_headers .mcp.json (in your project root)
- ChatGPT MailVakt analyze_email_headers Settings → Connectors → Advanced → Developer mode
- Claude.ai MailVakt analyze_email_headers Settings → Connectors → Add custom connector
- LangChain MailVakt analyze_email_headers pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mailvakt https://mcp.mailvakt.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 2 October 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.