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