Web Search MCP Server
Related Servers
Alternatives to Web Search MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables web searching through Google, DuckDuckGo, and Bing using a headless Chrome browser, returning structured results with titles, URLs, and snippets. Also supports fetching and extracting text content from any webpage.16MIT
- AlicenseAqualityDmaintenanceEnables comprehensive web and news searches via the Google Custom Search API with integrated content extraction using the Mozilla Readability algorithm. It allows users to perform quick snippet lookups or deep searches that fetch and format full article content into clean markdown.39 npm2MIT
- AlicenseBqualityDmaintenanceEnables Large Language Models to perform real-time web searches using Google Custom Search API. Integrates with Claude Desktop to retrieve current information from the internet.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables web searching through DuckDuckGo and fetching content from webpages. Provides search capabilities with configurable result limits and webpage content extraction for AI assistants.-
- AlicenseNot gradedqualityDmaintenanceEnables web searching using Google search results with no API keys required.11 npm1MIT
- AlicenseAqualityDmaintenanceEnables search capabilities using a Google Custom Search Engine, allowing users to input a search term and retrieve search result titles, links, and snippets, while facilitating integration with other tools for content extraction and advanced search strategies.147-
TDQS
Scored across 3 tools
The tools have significant overlap, particularly between web_search and web_search_and_scrape, which both perform search operations. While web_scrape is distinct for direct content extraction, the boundary between the two search tools is unclear, as web_search_and_scrape essentially combines the functionality of the other two, creating redundancy and potential confusion for agent selection.
All tool names follow a consistent snake_case pattern with a clear 'web_' prefix, indicating the domain. The naming is predictable and uniform across all three tools, making it easy to understand their purpose and relationship at a glance.
With only 3 tools, the count feels thin for a web search server, potentially limiting functionality. While it covers basic search and scrape operations, the scope might be too narrow, lacking tools for advanced features like filtering, pagination, or handling different content types, which could hinder comprehensive agent workflows.
The tool set has notable gaps for a web search domain, such as missing operations for filtering search results, handling pagination, or accessing cached content. The redundancy in search tools (web_search and web_search_and_scrape) suggests inefficiency rather than coverage, and there are no tools for managing search sessions or advanced metadata extraction, which could lead to agent failures in complex tasks.