web-scraper-server
Related Servers
Alternatives to web-scraper-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and human operators to drive isolated browser profiles with persistent cookies, fingerprints, and proxies, exposing navigation, clicking, typing, extraction, screenshots, JS evaluation, tabs, cookies, and waits to MCP clients.-
- AlicenseNot gradedqualityDmaintenanceProvides a real browser that bypasses bot detection (Cloudflare, Turnstile) for AI agents, enabling navigation, clicking, typing, screenshots, and data collection through MCP tools.180 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to automate web browsing with anti-detection behavior, including navigation, interaction, search, extraction, downloads, multi-tab workflows, and reusable sessions.549 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and human operators to drive isolated browser profiles with persistent cookies, fingerprints, and proxies through MCP, including navigation, clicking, typing, extraction, screenshots, JavaScript evaluation, tabs, cookies, and waits.MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to automate the web through an anti-detection browser, supporting navigation, interaction, search, extraction, downloads, multi-tab workflows, and session reuse.549 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to control an anti-detection browser for navigation, interaction, search, extraction, downloads, multi-tab workflows, and reusable sessions. It provides a practical browser automation toolset for automated web tasks while reducing blocking risks.549 npmMIT
TDQS
Scored across 62 tools
Multiple overlapping tool pairs exist, such as `screenshot` vs `browser_screenshot`, `click_element` vs `browser_click`, `get_sitemap` vs `crawl_site`, and `save_pdf` vs `download_file`. The split between browser-based and non-browser-based workflows adds confusion, forcing agents to choose between near-equivalent tools based on session state.
Tool names are predominantly snake_case with a verb_noun convention (`scrape_url`, `get_metadata`, `list_jobs`). The `browser_` prefix provides a consistent subgroup, and most deviations are minor (e.g., `health_check` instead of `check_health`). Long diagnostic tool names are slightly awkward but still follow the general pattern.
With 62 tools, the server far exceeds a coherent scope. Many tools are highly specialized diagnostics or configuration variants that could be consolidated. The sheer volume makes the surface overwhelming and dilutes the clarity of the core scraping workflow.
The tool set covers the full web scraping lifecycle: URL validation, fetching, content extraction, crawling, browser automation, job scheduling, configuration, caching, session management, and diagnostics. No major scraping capability appears to be missing, making the server functionally comprehensive.