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