check_ai_search_readiness — Site Check MCP Tool Read-only
check_ai_search_readiness
(check ai search readiness) is one of 4 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_search_readiness from your client
- Claude Code Site Check check_ai_search_readiness run in your project directory
- Claude Desktop Site Check check_ai_search_readiness ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Site Check check_ai_search_readiness ~/.cursor/mcp.json
- VS Code Site Check check_ai_search_readiness .vscode/mcp.json
- Zed Site Check check_ai_search_readiness ~/.config/zed/settings.json
- Windsurf Site Check check_ai_search_readiness ~/.codeium/windsurf/mcp_config.json
- Cline Site Check check_ai_search_readiness ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Site Check check_ai_search_readiness ~/.gemini/settings.json
- Grok Site Check check_ai_search_readiness .mcp.json (in your project root)
- ChatGPT Site Check check_ai_search_readiness Settings → Connectors → Advanced → Developer mode
- Claude.ai Site Check check_ai_search_readiness Settings → Connectors → Add custom connector
- LangChain Site Check check_ai_search_readiness pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http site-check https://mcp.modernmustardseed.com/site-checkOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.