Skip to main content
Glama
scrape-mcp
by guanyuyan

Related Servers

Alternatives to scrape-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to extract clean, structured web content (articles, tables, links, visual layouts) optimized for LLM token efficiency, with fast response times and optional JavaScript support.
      5
      72 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to fetch and process web content securely, including HTML-to-markdown conversion, reader mode, metadata extraction, RSS/sitemap parsing, and robots.txt-aware requests with SSRF protection.
      15
      3,650 npm
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to read web pages reliably, returning clean markdown content, hyperlinks, and metadata without navigation or ad noise.
      3
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to fetch and extract clean, readable text from arbitrary webpages while applying SSRF protection, hidden-content stripping, and prompt-injection scanning.
      328 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to fetch web pages, convert them into token-efficient semantic Markdown, and extract hyperlinks and page metadata while rotating realistic browser fingerprints to reduce anti-bot blocks.
      3
      140 PyPI
      MIT

    TDQS

    A3.9/5.0

    Scored across 21 tools

    Disambiguation4/5

    The core families are well delineated: fetch vs extract vs screenshot vs inspect each target a different output shape, and web_map vs web_index, web_watch vs web_changes vs web_history are explicitly contrasted in their descriptions. The residual overlaps are web_fetch vs web_batch vs web_crawl (sync bulk fetching) and web_crawl vs web_crawl_start (sync vs async versions of the same operation), which an agent can confuse at a glance. Descriptions do most of the disambiguation work rather than the names themselves.

    Naming Consistency4/5

    Almost everything is snake_case with a predictable noun/verb pairing (web_fetch, web_crawl_status, session_import), and related tools cluster into consistent families (web_crawl_*, web_crawl_*_status/list/cancel, session_*). Deviations: the bare 'login' verb breaks the session_* family it belongs to, and web_* mixes verb names (web_fetch, web_watch) with noun names (web_screenshot, web_history).

    Tool Count3/5

    21 tools is heavy for one server and sits in the borderline range. The async crawl quartet (web_crawl_start/status/cancel/list) largely duplicates the synchronous web_crawl, and web_batch overlaps with what web_crawl's link mode already does, so some of the surface is redundant rather than additive. Each remaining tool (search, fetch, extract, screenshot, inspect, map, index, watch/changes/history, schedule, session ops) does earn its place.

    Completeness4/5

    Coverage is unusually broad for a scraping server: discovery (search, map, index), retrieval (fetch, batch, crawl, async crawl), structured output (extract), rendering (screenshot, inspect), change tracking (watch, changes, history, schedule), and session lifecycle (login, import, export, list). Minor gaps: no session deletion/logout or snapshot cleanup beyond reset, no job deletion (only cancel), and no cache-clear or rate-limit inspection operation.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data