searxng-mcp-server
Related Servers
Alternatives to searxng-mcp-server
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceDeep Research infrastructure for AI agents. Search the web, read pages incrementally, follow source links, and collect relevant evidence across multiple sources. Web search runs through your own SearXNG instance, while the agent remains in control of research planning and reasoning. Cluefinch runs locally over MCP stdio.424 PyPIApache 2.0- FlicenseAqualityBmaintenanceAn MCP server for SearXNG that provides web search capabilities with concise model-visible output while preserving full result payloads in metadata. It supports search, parallel fetching, URL extraction, and research workflows through both local stdio and streamable HTTP transports.74-
- AlicenseBqualityCmaintenanceExposes SearXNG web search and query autocomplete to AI clients, returning ranked results, instant answers, and suggestions with filters for category, language, time range, engines, page, and safe search. It is distributed via npx and requires a self-hosted SearXNG instance with the JSON format enabled.28 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to run web searches across self-hosted SearXNG and/or You.com in parallel and to crawl single pages or whole sites into clean, deduplicated Markdown or JSON. It runs locally via STDIO or HTTP MCP transports, supports authenticated crawls, and requires no API key when using SearXNG.-
- AlicenseNot gradedqualityCmaintenanceA multi-function Streamable HTTP MCP tool aggregation server that provides web search via Brave, Exa, and SearXNG with multi-key rotation and cross-provider fallback, and supports extensible tool families (URL fetch, code search, RAG) through a pluggable architecture.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients and a terminal CLI to run web searches through a user's own SearXNG instance, saving every query as a reusable session and optionally generating AI-synthesized answers.40 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong one. Its purpose is stated clearly and unambiguously.
The single tool uses a clear, conventional verb name ('search') in snake_case, but with only one tool there is no pattern to demonstrate consistency across actions or resources.
A one-tool surface is thin even for a search-focused server; capabilities like fetching page content or querying instance configuration have no entry point. It is defensible for a minimal wrapper but leaves the server under-scoped.
Web search is covered, but the SearXNG domain typically includes parameters like category, language, time range, and pagination, plus follow-up needs such as retrieving a result page or listing available engines/instances. None of these secondary operations are exposed, creating potential dead ends.