WebSearch-MCP
Related Servers
Alternatives to WebSearch-MCP
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceEnables web search capabilities through the Tavily API, allowing users to search the web for information using natural language queries. Demonstrates MCP (Model Context Protocol) server implementation with stdio transport mode.4-
- AlicenseAqualityDmaintenanceA Grok-first multi-source search MCP for AI agents that integrates Grok, Tavily, AnySearch, and Firecrawl to provide unified search results, cross-verification, and web content fetching.3MIT
- FlicenseNot gradedqualityCmaintenanceMCP server exposing 8 Tavily tools (web search, fetch, crawl, map, QnA, context, and deep research) via Streamable HTTP for AI assistants to perform live web retrieval and research.1-
- FlicenseNot gradedqualityDmaintenanceEnables web search capabilities through the Tavily API, allowing users to search the web for information using natural language queries. Demonstrates MCP server implementation with stdio transport mode for integration with LLM applications.-
- FlicenseAqualityDmaintenanceEnables web search capabilities through the Tavily API and serves as a demonstration platform for building custom MCP tools. Designed for educational purposes to showcase MCP server development and LangGraph integration.6-
- FlicenseCqualityDmaintenanceEnables web search capabilities through the Tavily API. Allows users to search the web for information using natural language queries through the MCP protocol.3-
TDQS
Scored across 12 tools
The plan_* tools all contribute to building a structured search plan, but each has a distinct role (e.g., adding a term vs. adding a sub-query vs. mapping to a tool). The only potential confusion is between plan_search_term and plan_sub_query, but the descriptions generally clarify the difference.
All tool names use lowercase snake_case with consistent verb_noun or prefix patterns (plan_*, web_*, get_*, switch_*). No mixed conventions or vague verbs.
12 tools is well within the typical 3-15 range and each tool serves a clear purpose within the web search and planning workflow. The count feels neither bloated nor sparse.
The tool set covers the core lifecycle of planning, executing, and retrieving web search results. Minor gaps exist, such as the lack of a 'view plan' or 'reset plan' tool, but agents can work around these limitations.