MCP Web Search Tool
Related Servers
Alternatives to MCP Web Search Tool
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates with Brave Search API to provide real-time search capabilities through Server-Sent Events (SSE).236 npmGPL 3.0
- AlicenseBqualityDmaintenanceA 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.186 npm42ISC
- AlicenseAqualityDmaintenanceA Model Context Protocol server that enables web search, scraping, crawling, and content extraction through multiple engines including SearXNG, Firecrawl, and Tavily.4251 npm147MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform web searches using SearXNG, a privacy-respecting metasearch engine.143MIT
- FlicenseCqualityDmaintenanceA Model Context Protocol server that enables web search capabilities using the Tavily API, allowing AI models to retrieve current information from the internet through natural language commands.3-
- -licenseNot gradedqualityNot gradedmaintenanceA unified Model Context Protocol server that integrates multiple search providers including Brave, Tavily, Exa, Semantic Scholar, and arXiv. It enables users to perform web, news, and image searches alongside academic research and citation analysis through a single interface.-
TDQS
Scored across 5 tools
image_search, fetch_url, and list_providers are clearly distinct, but web_search and news_search overlap significantly: web_search explicitly says to use it first for 'news' and 'anything time-sensitive', while news_search claims news/headline queries. This contradictory guidance forces the agent to guess which to call for a news request.
All five names use consistent snake_case with a predictable action/resource pattern (news_search, image_search, web_search, list_providers, fetch_url). The convention is uniform throughout with no camelCase or stylistic drift.
Five tools is well-scoped for a web search server: three retrieval modes, one discovery/introspection tool, and one content-fetch tool. Each tool earns its place with no filler.
The surface covers the core search-and-read lifecycle (search web/news/images, inspect providers, fetch page content with pagination via next_cursor). Minor gaps exist, such as no structured result-set pagination for searches themselves, but core workflows are fully supported.