explain_finding — CrawlCheck MCP Tool
explain_finding
(explain finding) is one of 23 tools on the
CrawlCheck
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call explain_finding from your client
- Claude Code CrawlCheck explain_finding run in your project directory
- Claude Desktop CrawlCheck explain_finding ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CrawlCheck explain_finding ~/.cursor/mcp.json
- VS Code CrawlCheck explain_finding .vscode/mcp.json
- Zed CrawlCheck explain_finding ~/.config/zed/settings.json
- Windsurf CrawlCheck explain_finding ~/.codeium/windsurf/mcp_config.json
- Cline CrawlCheck explain_finding ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CrawlCheck explain_finding ~/.gemini/settings.json
- Grok CrawlCheck explain_finding .mcp.json (in your project root)
- ChatGPT CrawlCheck explain_finding Settings → Connectors → Advanced → Developer mode
- Claude.ai CrawlCheck explain_finding Settings → Connectors → Add custom connector
- LangChain CrawlCheck explain_finding pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crawlcheck https://crawlcheck.io/mcpOther tools on this server
- scan_domain
- verify_crawler_log
- corpus_state
- resolve_robots
- draft_llms
- fix_robots
- fix_entitymap
- video_check
- video_channel
- video_site
- registry_lookup
- crawler_path
- public_counts
- telemetry
- fix_mostly_code
- fix_stale_cache
- fix_machine_chain
- list_verified_capabilities
- machine_record
- resolve_domain
- preflight
- mcp_servers
This list was read from the server itself, by connecting to it and calling tools/list on 10 October 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.