wigolo
Related Servers
Alternatives to wigolo
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform local-first web search, fetch, crawl, extract, cache, research, and autonomous information gathering through MCP, with no API keys or cloud dependencies.1,154 npmAGPL 3.0
- 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
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to run offline-first web search, fetch and extract web content, build a local hybrid-retrieval knowledge base, and use persistent session memory without external API keys. It also supports intent-aware federated search, semantic reranking, entity graph exploration, and source-cited deep-search answers using local models.376 npm1ISC
- AlicenseAqualityAmaintenanceEnables AI agents to run local deep-research workflows via a single MCP stdio server, combining web search, page extraction, query-aware distillation, and caching without cloud quotas. It exposes tools for deep research, search, and single or batch URL reading.6MIT
- AlicenseAqualityAmaintenanceA local-first, no-API-key MCP server that enables LLMs to search the web, fetch pages, and read documents using multiple engines and smart fallbacks.11169MIT
- 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
TDQS
Scored across 10 tools
Core acquisition tools (fetch, crawl, search, cache) have clearly distinct roles, and descriptions explicitly steer between them (e.g. 'prefer over built-in WebFetch', 'run cache BEFORE any search'). However, `research` and `agent` overlap substantially — both plan queries, fetch sources in parallel, optionally apply a schema, and synthesize with optional LLM — and `find_similar` vs `cache` both search local cached content, so a few tools could be misselected without careful reading.
Mostly consistent single-word verb naming (fetch, crawl, search, extract, research, diff, watch), which reads predictably. Minor deviations: nouns used as tools (`cache`, `agent`) and one verb_adjective form (`find_similar`), but nothing chaotic.
Ten tools is well within a healthy scope for a web acquisition/research server, and each maps to a recognizable capability. The count is slightly inflated by pairs of near-variants (research/agent, cache/find_similar) that could arguably be consolidated into one tool each.
Strong lifecycle coverage for the domain: discovery (search), retrieval (fetch/crawl), offline reuse (cache), structured extraction (extract), comparison (diff), change monitoring with full job CRUD (watch), and synthesis (research/agent). Minor gaps: no explicit multi-URL batch fetch outside `agent`, and no declared handling for PDFs/documents or sitemap-only listing as a standalone operation.