validate_criteo_catalog — metasearch MCP MCP Tool
validate_criteo_catalog
(validate criteo catalog) is one of 12 tools on the
metasearch MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call validate_criteo_catalog from your client
- Claude Code metasearch MCP validate_criteo_catalog run in your project directory
- Claude Desktop metasearch MCP validate_criteo_catalog ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor metasearch MCP validate_criteo_catalog ~/.cursor/mcp.json
- VS Code metasearch MCP validate_criteo_catalog .vscode/mcp.json
- Zed metasearch MCP validate_criteo_catalog ~/.config/zed/settings.json
- Windsurf metasearch MCP validate_criteo_catalog ~/.codeium/windsurf/mcp_config.json
- Cline metasearch MCP validate_criteo_catalog ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI metasearch MCP validate_criteo_catalog ~/.gemini/settings.json
- Grok metasearch MCP validate_criteo_catalog .mcp.json (in your project root)
- ChatGPT metasearch MCP validate_criteo_catalog Settings → Connectors → Advanced → Developer mode
- Claude.ai metasearch MCP validate_criteo_catalog Settings → Connectors → Add custom connector
- LangChain metasearch MCP validate_criteo_catalog pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http metasearch-mcp https://metasearch.com.tr/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 8 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.