Skip to main content
Glama

Related Servers

Alternatives to deep-websearch

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables federated multi-source research by fanning out queries across web, community, and social sources, deduplicating and interleaving results, and storing a persistent corpus for cross-checking.
      6
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run unified web searches across multiple providers such as Exa, Serper, Tavily, Firecrawl, and Jina, fusing results with reciprocal rank fusion, and to extract readable content from public web pages, PDFs, and video pages as Markdown. Provider chains are configurable, failures are isolated per provider, and responses report attempted, succeeded, failed, and skipped channels with source tracing and honest warnings.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to run local-first web research: intent-routed search across independent engines with reranking, a multi-stage fetch/crawl ladder, and document extraction. Results come back as signed-cursor, citation-bearing evidence envelopes, with an optional separately enabled profile for browser click/type actions.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform web search, extraction, and research across multiple provider backends with persistent multi-key rotation and auditable routing. Supports MCP, CLI, and Agent Skill entry points.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to perform comprehensive web research through tiered search, secure URL fetching with markdown conversion, and automated multi-source synthesis pipelines. Provides read-only tools with configurable caching, SSRF protection, and optional LLM-powered summarization for search results and content analysis.
      8
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct operation: source_status is diagnostics, broad_search is search, and fetch_page/fetch_pages are single vs. batched retrieval. The fetch_page vs. fetch_pages pair could be momentarily confused, but descriptions clearly distinguish single-URL extraction from batch reading up to 10 pages.

    Naming Consistency4/5

    All names use consistent snake_case (source_status, broad_search, fetch_page, fetch_pages), and the fetch_ prefix cleanly pairs the single/batch variants. source_status is noun_noun rather than the verb_noun pattern of the others, a minor deviation.

    Tool Count4/5

    Four tools is a lean but sensible scope for a search-and-fetch server: one diagnostic, one search, and two retrieval tools. It is slightly thin (no dedicated source-listing or pagination tool), but each tool clearly earns its place.

    Completeness4/5

    The surface covers the core lifecycle: check source readiness, run broad search with citations, and extract evidence from single or multiple pages. Minor gaps exist (e.g., explicit source enumeration or result pagination), but agents can work around these via source_status and broad_search parameters.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues