mcp-omnisearch

Based on the available evidence, mcp-omnisearch looks more like an early open-source component worth evaluating than a broadly validated production search layer. The usable evidence is almost entirely the official GitHub repository description. That supports its positioning and claimed integrations, but not reliability, result quality, maintenance depth, or real-world adoption. So the adoption judgment should be conservative: it is relevant for MCP agent experiments, but the evidence is too thin to treat it as production-proven.

In practical terms, this is not a search engine and not a standalone AI chat product. It is better understood as an MCP-facing integration layer for search and extraction. The repository text says it provides unified access to providers such as Tavily, Brave, Kagi, and Exa, plus some AI tools and content extraction services, so agents can query them through one MCP server. A more accurate analogy is “a search routing and wrapper layer for agents,” not “a consumer search product that replaces Google.”

On cost and setup, the evidence only supports a cautious read.