crawler_path — CrawlCheck MCP Tool
crawler_path
(crawler path) 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 crawler_path from your client
- Claude Code CrawlCheck crawler_path run in your project directory
- Claude Desktop CrawlCheck crawler_path ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CrawlCheck crawler_path ~/.cursor/mcp.json
- VS Code CrawlCheck crawler_path .vscode/mcp.json
- Zed CrawlCheck crawler_path ~/.config/zed/settings.json
- Windsurf CrawlCheck crawler_path ~/.codeium/windsurf/mcp_config.json
- Cline CrawlCheck crawler_path ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CrawlCheck crawler_path ~/.gemini/settings.json
- Grok CrawlCheck crawler_path .mcp.json (in your project root)
- ChatGPT CrawlCheck crawler_path Settings → Connectors → Advanced → Developer mode
- Claude.ai CrawlCheck crawler_path Settings → Connectors → Add custom connector
- LangChain CrawlCheck crawler_path 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
- public_counts
- telemetry
- fix_mostly_code
- fix_stale_cache
- fix_machine_chain
- explain_finding
- 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.