mcp-searxng and mcp-omnisearch
These are competitors offering overlapping search functionality—SearXNG provides a metasearch aggregator interface while omnisearch wraps multiple proprietary search APIs—so users would typically choose one based on whether they prefer decentralized/self-hosted search (SearXNG) or managed commercial search services (omnisearch).
About mcp-searxng
ihor-sokoliuk/mcp-searxng
MCP Server for SearXNG
Exposes two MCP tools: `searxng_web_search` with filtering by time range, language, and safe search level; and `web_url_read` for extracting markdown content with section filtering and paragraph range selection. Implements TTL-based caching for URL content and supports configurable proxy routing per tool, HTTP Basic Auth, and custom User-Agent headers for both search and content extraction interfaces.
About mcp-omnisearch
spences10/mcp-omnisearch
🔍 A Model Context Protocol (MCP) server providing unified access to multiple search engines (Tavily, Brave, Kagi), AI tools (Perplexity, FastGPT), and content processing services (Jina AI, Kagi). Combines search, AI responses, content processing, and enhancement features through a single interface.
# Technical Summary Implements four consolidated MCP tools (web_search, ai_search, github_search, web_extract) with pluggable provider backends, allowing clients to query multiple APIs through a unified interface while gracefully degrading based on available credentials. Supports advanced search operators native to Brave/Kagi, domain filtering via API parameters, and specialized extractors like Firecrawl's interactive scraping and Kagi's multimodal summarization (pages, videos, podcasts). Designed for integration with AI assistants (Claude Desktop, Cline) via environment-variable configuration with zero hard dependencies on any single provider.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work