searxng-mcp-server
Related Servers
Alternatives to searxng-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP-compatible clients to perform web searches through a self-hosted SearXNG instance, with support for configurable languages, categories, time ranges, and safe search settings.2273 npmMIT
- AlicenseAqualityCmaintenanceEnables MCP clients to perform web searches through a self-hosted SearXNG instance, offering privacy-focused metasearch without API keys or vendor lock-in.3BSD 3-Clause
- AlicenseAqualityBmaintenanceMCP server for privacy-respecting web search via SearXNG, providing web, news, and image search with engine listing capabilities.4MIT
- AlicenseNot gradedqualityDmaintenanceFree web search MCP server using SearXNG, supporting web search, news search, and search summaries.MIT
- AlicenseAqualityCmaintenanceMCP server for local web search via SearXNG, providing unlimited queries without API keys or cost, with automatic fallback to public instances.31MIT
- FlicenseNot gradedqualityDmaintenancePrivacy-focused web search MCP server using SearXNG with Streamable HTTP transport, supporting authentication and advanced search parameters.-
TDQS
Scored across 13 tools
The typed *_search tools (image/music/news/paper/video) overlap with the generic search, but descriptions explicitly direct users to prefer the dedicated tools, making boundaries clear. The fetch-family tools (search_and_fetch, fetch_content, crawl_site, deep_search) also overlap somewhat but each has a distinct stated use case (snippets vs. full page vs. site survey vs. multi-source research).
Nearly all names are snake_case with a clear noun+search or verb+noun pattern (image_search, fetch_content, crawl_site, list_engines). Minor deviations are single-word names (autocomplete, doctor) and noun-first ordering, but overall the convention is predictable and readable.
13 tools is a well-scoped count for a web-search server, covering vertical searches, fetching, crawling, diagnostics and autocomplete without redundancy bloat. Each tool earns its place with a distinct capability.
The surface covers a broad domain: multi-vertical search, autocomplete, content fetching/crawling, deep research and instance diagnostics, forming a coherent lifecycle. Minor gaps like batch ref fetching or structured result caching controls exist but are workable around.