ScrapeUnblocker MCP Server
OfficialRelated Servers
Alternatives to ScrapeUnblocker MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with reliable web fetching capabilities, handling retries, caching, and anti-bot bypass automatically.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search the web, read and extract content from webpages, fetch JSON from REST APIs, and collect links while bypassing anti-bot protections.18 npmISC
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to fetch any web page (including those behind Cloudflare or CAPTCHAs), extract clean markdown, structured data, crawl sites, and map URLs via BypassAPI.MIT
- AlicenseNot gradedqualityBmaintenanceEnables fetching and rendering web pages via ScrapingBee, extracting structured data with AI, and scraping Google search results through MCP.56 npmMIT
- AlicenseAqualityAmaintenanceEnables AI models to fetch real web pages while automatically bypassing anti-bot protections, login walls, and JS rendering, then returns clean, token-efficient article content.4MIT

@unblockingapi/mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to fetch bot-protected web pages, run structured Google searches, and check domain authority through UnblockingAPI's anti-detection engine and residential proxies.3219 npm1MIT
TDQS
Scored across 4 tools
Each tool targets a distinct action: fetch_html (raw HTML), fetch_parsed (structured JSON), google_search (URL discovery), and list_elements (read-only selector discovery). The descriptions explicitly cross-reference each other (e.g. 'use fetch_html for the page itself'), making selection unambiguous.
All four names are snake_case and follow a verb_noun pattern (fetch_html, fetch_parsed, list_elements, google_search). The convention is uniform and predictable.
Four tools is lean and each earns its place for a scraping service, covering fetch, parse, search, and element discovery. It sits at the low end of the ideal range but is well-scoped rather than thin.
The surface covers the core scraping lifecycle: discovery (google_search), selector inspection (list_elements), raw fetch, and parsed extraction with interactive steps. Minor gaps like multi-page crawling or pagination/session handling exist but core workflows are covered.