Skip to main content
Glama
ScrapingBot MCP Server

ScrapingBot MCP Server

by sostag

Related Servers

Alternatives to ScrapingBot MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to scrape web pages into Markdown, text, HTML, JSON, PDFs, screenshots, and structured data, while managing batch scraping jobs, persistent browser sessions, usage/request history, and docs lookup through native MCP tools.
      27
      415 npm
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to scrape, crawl, map, search, and extract web pages as clean markdown or structured JSON directly through MCP tools.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to extract structured data from web pages by giving a URL and a natural-language prompt describing the fields to retrieve. It exposes this capability as an MCP tool that plugs into clients like Claude, VS Code, Cursor, and Windsurf.
      227 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to extract structured, prompt-defined data from any web page by supplying a URL and a description of the fields to retrieve. It exposes this capability as a single tool for use in MCP-compatible clients such as Claude, VS Code, Cursor, and Windsurf.
      227 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to search, scrape, crawl, map, and interact with live web pages, returning clean, structured, agent-ready content. It also supports recurring page monitoring, autonomous deep research, and credit-usage checks.
      26
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents and MCP clients to fetch webpages and crawl sites, extract main content, and convert it into clean Markdown with preserved links for fast, token-efficient scraping.
      -

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target clearly distinct verticals, and descriptions explicitly route users (use scrape_social_media for social networks, scrape_search_engine instead of scrape_raw_html for Google/Bing). The main overlaps are scrape_retail vs scrape_grocery (both extract product title/price/brand from e-commerce pages) and scrape_booking vs scrape_real_estate (Airbnb/Abritel rentals vs property listings), which could cause occasional misselection on borderline pages.

    Naming Consistency5/5

    All ten tools follow a strict snake_case verb_noun pattern (get_account, get_usage_history, get_social_media_result, scrape_*), with scraping tools grouped under a single scrape_ prefix by vertical. No mixed conventions or camelCase.

    Tool Count5/5

    Ten tools is well within the ideal range, and each earns its place: two zero-credit account/diagnostic tools, one async result poller, and seven scrapers covering distinct content verticals plus a raw fallback.

    Completeness4/5

    The surface covers account/credit inspection, usage diagnostics, retry of pending jobs, and the major scraping verticals plus a raw HTML fallback, which is solid end-to-end coverage for a scraping API. The gap is that async pending-result retrieval (get_social_media_result) exists only for social media, so long-running or expensive retail/real-estate/booking jobs have no documented way to be picked up later.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data