check_m365 — TamingDNS MCP Tool Read-only

check_m365 (check m365) 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 check_m365 from your client

Claude Code TamingDNS check_m365 run in your project directory
Claude Desktop TamingDNS check_m365 ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor TamingDNS check_m365 ~/.cursor/mcp.json
VS Code TamingDNS check_m365 .vscode/mcp.json
Zed TamingDNS check_m365 ~/.config/zed/settings.json
Windsurf TamingDNS check_m365 ~/.codeium/windsurf/mcp_config.json
Cline TamingDNS check_m365 ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI TamingDNS check_m365 ~/.gemini/settings.json
Grok TamingDNS check_m365 .mcp.json (in your project root)
ChatGPT TamingDNS check_m365 Settings → Connectors → Advanced → Developer mode
Claude.ai TamingDNS check_m365 Settings → Connectors → Add custom connector
LangChain TamingDNS check_m365 pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http mcp https://tamingdns.com/mcp

Other tools on this server

check_spf
check_dkim
discover_dkim
check_dmarc
check_tls_rpt
check_mta_sts
check_bimi
check_dane
check_dnssec
check_mx
check_google_workspace
check_dns_propagation
check_txt
decode_bounce
analyze_dmarc_report
check_website
check_mcp_keys
analyze_email_headers

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.

TamingDNS MCP server