Skip to main content
Glama

Related Servers

Alternatives to Web Researcher MCP

  • A
    license
    A
    quality
    F
    maintenance
    Tools for AI assistant's deep research: * Google search + webpage reading (incl. JS-rendered pages) * Document & decks analysis * YouTube transcript extraction * Patents + academic paper search * Company and competitors research * Prompts for comprehensive-research, fact-check, summarize-url, news-briefing, patent-portfolio-analysis, competitive-analysis, literature-review, technical-deep-dive
    8
    36
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables LLMs to run web and academic searches across multiple engines (Baidu, Bing, DuckDuckGo, Tavily, Exa, Doubao and 9 scholarly sources) with local relevance scoring, deduplication and caching, plus SSRF-protected page fetching and PDF parsing, and works without any API key. It plugs into MCP clients like Claude Code, Cursor and Qwen Code, or can be embedded as a Go module.
    30
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Zero-auth multi-source research MCP server that enables web search, reading URLs, PDFs, GitHub repos, and querying Hacker News, Stack Overflow, Semantic Scholar, and YouTube transcripts without API keys.
    43 PyPI
    12
    Apache 2.0
  • A
    license
    Not graded
    quality
    F
    maintenance
    MCP server enabling local-first web search, fetch, extract, and caching with citeable excerpts, no API key required. Supports research workflows for agents and apps.
    67 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    A production-ready Model Context Protocol server that brings AI-powered web search directly into development environments, providing intelligent search results with proper citations in Claude Desktop, Cursor, or any MCP-compatible client.
    61 npm
    21
    MIT

TDQS

A4.2/5.0

Scored across 25 tools

Disambiguation4/5

The tool set is broadly differentiated by vertical domains (academic, news, legal, clinical, patent, economic, local, image) and by lifecycle role (discover, scrape, verify, format, export). A few clusters could still be confused at first glance—notably web_search vs search_and_scrape vs scrape_page, and academic_search vs paper_fulltext vs citation_graph—but the descriptions explicitly delineate when to use each.

Naming Consistency4/5

All names use snake_case and are readable and predictable. Most search endpoints follow a <domain>_search pattern, while action tools use verb_noun; the mix is coherent rather than chaotic, though it is not a single uniform verb_noun convention.

Tool Count3/5

Twenty-five tools is heavy for a single MCP server, even one covering broad web research. Many vertical search integrations earn their place, but the surface is at the upper end of what an agent can scan and choose among comfortably.

Completeness5/5

The set covers the research lifecycle end to end: vertical discovery, full-text retrieval, citation verification and bibliography auditing, session tracking and recovery, bibliography formatting, report export, and archival. There are no obvious dead ends for the stated web-research purpose; gaps like social-search breadth are minor and partly handled by scraping.

Maintenance

ActivityActive
ResponsivenessUsually handled