searxng-mcp-bridge
Related Servers
Alternatives to searxng-mcp-bridge
No user-submitted related servers found.
Related Servers
- 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
- AlicenseNot gradedqualityDmaintenanceEnables privacy-focused web search via SearXNG for MCP clients, allowing users to perform searches with customizable parameters through natural language.221 npmMIT
- AlicenseAqualityDmaintenanceIntegrates with SearXNG metasearch engine to provide powerful web search capabilities across multiple search engines with filtering options for categories, languages, time ranges, and safe search levels. Enables comprehensive web searches, autocomplete suggestions, and search engine configuration access through MCP-compatible applications.41MIT
- FlicenseNot gradedqualityDmaintenanceProvides a free web search tool to MCP clients by connecting to a self-hosted SearXNG metasearch instance, enabling users to search the web with customizable parameters like categories and time range.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to perform web searches through a self-hosted SearXNG backend with automatic Bing fallback, protected by API key authentication.21 npmMIT
- AlicenseBqualityBmaintenanceAn MCP server that integrates with the SearXNG API to provide comprehensive web search capabilities with features like time filtering, language selection, and safe search. It also enables users to fetch and convert web content from specific URLs into markdown format.221 npm4MIT
TDQS
Scored across 2 tools
search and health_check have clearly distinct purposes: one performs searches, the other reports connectivity/health. There is no realistic overlap that would cause an agent to misselect between them.
Both names use snake_case, which is consistent. However, search is a bare verb while health_check is a verb/noun-style check name, so the pattern is mostly but not perfectly consistent.
Two tools is slightly thin in general, but the server is narrowly scoped as a SearxNG bridge. search and health_check both earn their place and cover the essential surface without bloat.
The core lifecycle for this bridge is covered: perform a search and verify health/connectivity. Minor optional gaps might include exposing advanced search parameters or instance/engine metadata, but nothing essential is missing.