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