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