Scrapeless MCP Server
Related Servers
Alternatives to Scrapeless MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude to perform web research by integrating Google search, extracting webpage content, and capturing screenshots.31,175 npm20MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables Claude to perform web research by integrating Google search, extracting webpage content, and capturing screenshots in real-time.41,175 npm9MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that provides web and image search capabilities through Google's Custom Search API, allowing AI assistants like Claude to access current information from the internet.22-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for integrating Google Search capabilities into AI applications.-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform web searches using Google Search API, returning up to 20 search results in JSON format.2Apache 2.0
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables LLMs to perform web searches using Google's Custom Search API through a standardized interface.147MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'google-search' has a clear and distinct purpose of fetching Google search results, so agents cannot misselect between multiple options.
The single tool name 'google-search' follows a consistent pattern of verb-noun (search as the verb, Google as the noun context), and with only one tool, there is no inconsistency to evaluate. The naming is clear and adheres to a predictable structure.
The server has only one tool, which feels thin and under-scoped for a scraping-related domain. A single tool for fetching Google search results may not provide sufficient coverage for typical scraping workflows, such as parsing results, handling pagination, or interacting with other search engines, making it borderline too few for the apparent purpose.
Inferring the domain as web scraping or search data fetching, the tool surface is severely incomplete. It only offers a basic search fetch without supporting operations like filtering results, extracting specific data, managing queries, or integrating with other scraping tasks, leading to significant gaps that could cause agent failures in broader scraping scenarios.