Skip to main content
Glama
ScrapeOps

ScrapeOps MCP Server

by ScrapeOps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to ScrapeOps MCP Server

No user-submitted related servers found.

    Related Servers

    • FineData MCP Server

      quality-network
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to scrape any website by providing tools for JavaScript rendering, antibot bypass, and automatic captcha solving. It supports synchronous, asynchronous, and batch scraping operations with built-in proxy rotation.
      5
      207 npm
      MIT

    • Browser MCP Server

      feedmepos
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to operate a real, anti-bot-aware browser through Zyte API for navigating pages, clicking, typing, scrolling, taking screenshots, searching, and extracting structured data, with automatic proxy rotation and ban avoidance.
      24 npm
      -

    • webscout-mcp

      wxs-lang
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to perform web searches, fetch and extract page content, and crawl sites with caching, rate limiting, and robots.txt compliance, all without needing API keys.
      11
      520 PyPI
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: maps_web for general browsing and scraping, extract_data for structured data extraction, and return_links for URL extraction. There is no functional overlap.

    Naming Consistency4/5

    All tools follow a verb_noun pattern with underscores (maps_web, extract_data, return_links). However, 'maps_web' is a slightly ambiguous verb choice, deviating from the more descriptive verbs like 'extract' and 'return'.

    Tool Count4/5

    Three tools is low but sufficient for a focused scraping toolkit. They cover the core tasks: browsing, data extraction, and link analysis. Additional tools (e.g., dedicated screenshot) could be added, but the current count is reasonable.

    Completeness4/5

    The tool surface covers the primary scraping workflows: browsing with advanced features (maps_web), structured extraction (extract_data), and link discovery (return_links). Minor gaps exist, such as lack of form interaction or session management, but core needs are met.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources