keyless-web-search-mcp
Related Servers
Alternatives to keyless-web-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables any MCP client to run keyless multi-engine web searches with RRF fusion, fetch pages and documents as Markdown, and full-text search a local SQLite index. It keeps queries and cached content on the user's machine, degrading gracefully across engine tiers when providers are blocked or rate-limited.8MIT
- AlicenseAqualityBmaintenanceEnables web search without API keys using DuckDuckGo and Bing search engines, and retrieves webpage content. Supports multiple search engines simultaneously with privacy protection and asynchronous processing.2120 PyPI10MIT
- AlicenseAqualityCmaintenanceEnables keyless multi-engine web, news, image, and video metasearch plus full-page markdown extraction for AI agents over MCP, with resilient fallback across DuckDuckGo, Bing, Brave, Google, and other backends.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables LLMs and coding assistants to run web searches by concurrently aggregating multiple commercial search engines per scenario, merging and deduplicating URL-normalized results with per-call fallback. When no API keys or all commercial engines fail, it automatically degrades to key-free DuckDuckGo and Bing channels so search never goes offline.18 npmMIT
- AlicenseAqualityCmaintenanceFree web search, web-page reading as Markdown, and llms.txt documentation retrieval for MCP clients. Runs locally with Node.js over stdio using @alkasima/alka-search-mcp. Searches DuckDuckGo, Mojeek, and Brave; default providers require no API key. Website and provider availability may vary.83MIT
- AlicenseNot gradedqualityAmaintenanceGives AI assistants keyless web search, news search, and full-page reading tools by querying multiple engines in parallel and returning merged results. It can run locally over stdio or remotely over HTTP for Claude, Cursor, and other agents.3MIT
TDQS
Scored across 2 tools
The two tools are completely distinct: web_search performs web searches across multiple engines, while web_fetch retrieves the content of a specific URL. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun pattern: web_search and web_fetch. The naming is clear, consistent, and predictable.
The server has only two tools, which is slightly below the typical well-scoped range of 3-15. However, each tool is essential and covers the core functionality of keyless web search and fetching, so the count is reasonable for the narrow scope.
The tool surface fully covers the stated purpose of keyless web search: web_search finds relevant results and web_fetch retrieves full page content. There are no obvious missing operations for this domain.