free-search-mcp
Related Servers
Alternatives to free-search-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP server enabling local-first web search, fetch, extract, and caching with citeable excerpts, no API key required. Supports research workflows for agents and apps.65 npm1MIT
- AlicenseAqualityAmaintenanceAn MCP server providing web search, image search, and page scraping tools to LLMs without requiring API keys.12323MIT
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP server that enables LLMs to search the web via DuckDuckGo, search GitHub code repositories, and extract clean content from web pages in LLM-friendly formats.9MIT
- AlicenseAqualityAmaintenanceA local-first MCP server that lets AI agents read any webpage as clean Markdown, crawl whole sites within configured limits, search without API keys, and solve supported captchas locally — all without cloud services or third-party keys.3020AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceA zero-config web search and fetch MCP server for LLM agents, featuring multi-backend metasearch, persistent rolling cache, and structured error envelopes for retry-friendly interactions.MIT
- AlicenseAqualityBmaintenanceA local-first MCP server for web search and documentation fetching, providing free DuckDuckGo search, URL-to-markdown conversion, and library docs from npm, PyPI, crates.io, Go, and GitHub with caching.5MIT
TDQS
Scored across 11 tools
Each tool has a sharply bounded purpose, and the descriptions actively preempt confusion with explicit 'Not recommended for' cross-references (fetch vs fetch_batch vs compare vs research, read_doc vs fetch on documents, search vs cache_search). The one genuinely thin boundary — compare vs fetch_batch for multi-URL reads — is spelled out by URL-count and output-shape rules.
All names are lowercase snake_case with a consistent style, and most follow verb_noun or verb_object (fetch_batch, cache_search, read_doc, extract_structured). A few are bare verbs or nouns (search, fetch, compare, download, engines, research) and paper_graph is noun_noun, but the set still reads predictably.
Eleven tools is squarely in the sweet spot for a search-and-retrieval server. Every tool maps to a distinct workflow primitive (discover, read, batch, compare, extract, cache, cite, save) with no filler.
The surface covers the full lifecycle: discovery (search/research/engines), retrieval (fetch/fetch_batch/read_doc with pagination), inspection (extract_structured), local corpus reuse (cache_search), citation tracing (paper_graph), and file persistence (download). Only very minor cache-management gaps exist (no listing or eviction of cached pages), which agents can work around.