namesniper_check_domains — NameSniper MCP Tool
namesniper_check_domains
(namesniper check domains) is one of 11 tools on the
NameSniper
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call namesniper_check_domains from your client
- Claude Code NameSniper namesniper_check_domains run in your project directory
- Claude Desktop NameSniper namesniper_check_domains ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NameSniper namesniper_check_domains ~/.cursor/mcp.json
- VS Code NameSniper namesniper_check_domains .vscode/mcp.json
- Zed NameSniper namesniper_check_domains ~/.config/zed/settings.json
- Windsurf NameSniper namesniper_check_domains ~/.codeium/windsurf/mcp_config.json
- Cline NameSniper namesniper_check_domains ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NameSniper namesniper_check_domains ~/.gemini/settings.json
- Grok NameSniper namesniper_check_domains .mcp.json (in your project root)
- ChatGPT NameSniper namesniper_check_domains Settings → Connectors → Advanced → Developer mode
- Claude.ai NameSniper namesniper_check_domains Settings → Connectors → Add custom connector
- LangChain NameSniper namesniper_check_domains pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http namesniper https://namesniper.pro/mcpOther tools on this server
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.