Tavily Search MCP Server
Related Servers
Alternatives to Tavily Search MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server enabling advanced search and content extraction using the Tavily API, with rich customization and integration options.99 npm12MIT
- FlicenseCqualityBmaintenanceA Model Context Protocol server that enables LLMs to perform Google searches via the Serper API, allowing models to retrieve current information from the web.1339-
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables web search, scraping, crawling, and content extraction through multiple engines including SearXNG, Firecrawl, and Tavily.4121 npm141MIT
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to perform real-time web searches, retrieving up-to-date information from the internet via a Crawler API.175 npm41ISC
- -licenseBqualityNot gradedmaintenanceA Model Context Protocol compliant server that facilitates comprehensive web research by utilizing Tavily's Search and Crawl APIs to gather and structure data for high-quality markdown document creation.147 npm12-
- AlicenseAqualityCmaintenanceA Model Context Protocol server that provides real-time web search capabilities to AI assistants through pluggable search providers, currently integrated with the Brave Search API.516MIT
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes with no overlap: roll_dice handles random number generation, web_search performs internet queries, and YOUR_TOOL_NAME (though placeholder) appears to be a distinct third function. Each tool targets a completely different domain, making misselection unlikely.
Naming conventions are inconsistent: roll_dice uses snake_case with a verb_noun pattern, web_search also uses snake_case verb_noun, but YOUR_TOOL_NAME uses a different style (all caps with underscores). While two tools follow a pattern, the third breaks it completely, creating naming chaos.
With only three tools, this feels thin for a 'Tavily Search MCP Server' - the name suggests search-focused functionality, but only one tool (web_search) directly supports this. The inclusion of dice rolling seems out of scope, making the tool count borderline appropriate but poorly aligned with the server's stated purpose.
For a search server, there are significant gaps: only basic web_search is provided, with no advanced search options, filtering, result processing, or search history management. The placeholder tool and dice rolling don't address core search functionality, leaving the surface incomplete for search-related workflows.