Skip to main content
Glama
qqkkrr

universal-scraper

by qqkkrr

Related Servers

Alternatives to universal-scraper

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server to scrape web pages to clean Markdown via headless Chromium, with support for single or batch URLs.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      MCP server for remote web scraping, providing a scrape_web tool that fetches pages and extracts content as markdown or JSON, supporting CSS selectors.
      1
      -
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for web scraping with natural language, enabling site crawling, page fetching, and extraction of emails, phones, links, and social profiles. Returns clean markdown, handles JavaScript rendering, and respects rate limits.
      24
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for retrieving web pages as clean Markdown, with configurable detail levels and optional Chromium rendering for JavaScript-heavy pages.
      1
      MIT

    TDQS

    A3.5/5.0

    Scored across 8 tools

    Disambiguation3/5

    Most tools have distinct roles (crawl, bulk_scrape, screenshot, check, books), but scrape and extract overlap heavily because both turn web content into clean Markdown/text/tables, differing mainly by URL vs HTML input. The auto tool also overlaps conceptually with scrape/crawl by generating and running scraping tasks, so agents may hesitate between auto, scrape, and extract.

    Naming Consistency2/5

    Names mix single verbs (scrape, crawl, check, extract), a noun-like tool (books), a vague automation label (auto), and one snake_case compound (bulk_scrape). The set is readable but has no predictable verb_noun or resource_action convention.

    Tool Count5/5

    Eight tools is well-scoped for a universal scraper, covering single-page scraping, batch scraping, recursive crawling, extraction, screenshots, diagnostics, AI-assisted automation, and a book-data specialization. Each tool has a plausible place in the workflow.

    Completeness4/5

    The surface covers the core scraping lifecycle: fetch one page, fetch many, crawl a site, extract from HTML, screenshot, diagnose, and automate configuration. Minor gaps exist around explicit session/cookie/proxy management or structured job status, but the main workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive