Web Researcher MCP
Related Servers
Alternatives to Web Researcher MCP
- AlicenseAqualityFmaintenanceTools 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-dive8157 npm36MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables 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.27MIT
- 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.11167MIT
- AlicenseNot gradedqualityCmaintenanceZero-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.75 PyPI11Apache 2.0
- AlicenseBqualityFmaintenanceA Model Context Protocol (MCP) server for web research. Bring real-time info into Claude and easily research any topic.3278 npm298MIT
- 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 gradedqualityCmaintenanceA 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.149 npm22MIT
TDQS
Scored across 25 tools
With 25 tools there is real density, but each search tool targets a distinct vertical/source (web, news, academic, clinical, legal, patent, econ, local, image, awesome lists, monarch) and descriptions explicitly cross-reference each other to redirect the agent. The near-neighbors (verify_citation vs audit_bibliography vs verify_recommendation; scrape_page vs search_and_scrape vs paper_fulltext) are clearly scoped and differentiated in their descriptions. Only minor edge ambiguity remains among the many *_search tools.
Names are uniformly snake_case with a dominant, predictable X_search convention, plus consistent verb_noun forms (scrape_page, verify_citation, format_bibliography, archive_source). A few are noun phrases (citation_graph, paper_fulltext, research_export) rather than verb_noun, a minor deviation. No mixed casing or chaotic verb styles.
At exactly 25 tools this sits at the heavy end of the rubric. Each tool maps to a genuinely distinct data source or lifecycle step, so few feel redundant, but the surface is large enough that agents must navigate many similar-sounding options. Borderline rather than clearly over-scoped.
The surface covers the full research lifecycle: discovery (web/news/academic/vertical searches), reading (scrape_page, search_and_scrape, paper_fulltext), verification (verify_citation, audit_bibliography, verify_recommendation), citation (format_bibliography), archiving (archive_source), session tracking (sequential_search, get_research_session), and export (research_export). No obvious dead ends remain for a research server's purpose.