mcp-searxng and serper-mcp-server
These are competitors offering alternative search backends for MCP integrations—SearXNG provides a self-hosted, privacy-focused metasearch option while Serper offers a commercial API-based search service, so users would typically choose one based on deployment preferences and API availability rather than use both together.
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 serper-mcp-server
garylab/serper-mcp-server
A Serper MCP Server
Implements 11 specialized search tools covering web, images, videos, maps, news, shopping, scholar, patents, and webpage scraping—all exposed via the Model Context Protocol for seamless LLM integration. Built as a Python MCP server that communicates through stdio with Serper's Google Search API, configurable for Claude Desktop and other MCP clients via environment variables. Deployable via `uvx`, `pip`, or directly from source with zero-configuration setup.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work