dns_diagnose_sip_target — Sipflow MCP Tool
dns_diagnose_sip_target
(dns diagnose sip target) is one of 22 tools on the
Sipflow
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call dns_diagnose_sip_target from your client
- Claude Code Sipflow dns_diagnose_sip_target run in your project directory
- Claude Desktop Sipflow dns_diagnose_sip_target ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sipflow dns_diagnose_sip_target ~/.cursor/mcp.json
- VS Code Sipflow dns_diagnose_sip_target .vscode/mcp.json
- Zed Sipflow dns_diagnose_sip_target ~/.config/zed/settings.json
- Windsurf Sipflow dns_diagnose_sip_target ~/.codeium/windsurf/mcp_config.json
- Cline Sipflow dns_diagnose_sip_target ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sipflow dns_diagnose_sip_target ~/.gemini/settings.json
- Grok Sipflow dns_diagnose_sip_target .mcp.json (in your project root)
- ChatGPT Sipflow dns_diagnose_sip_target Settings → Connectors → Advanced → Developer mode
- Claude.ai Sipflow dns_diagnose_sip_target Settings → Connectors → Add custom connector
- LangChain Sipflow dns_diagnose_sip_target pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sipflow https://mcp.sipflow.dev/mcpOther tools on this server
- search_sip_docs
- lookup_response_code
- lookup_sip_header
- detect_sip_stack
- detect_sip_vendor_from_config
- minimize_sip_trace
- render_sip_ladder
- sip_ladder_example
- lint_sip_request
- parse_sip_message
- diff_sip_messages
- review_sip_config
- webrtc_sip_checklist
- parse_sdp
- compare_sdp_offer_answer
- validate_stir_shaken_identity
- stir_attestation_explainer
- validate_e164_number
- troubleshoot_response_code
- fetch_sipflow_share
- submit_sipflow_feedback
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.