Skip to main content
Glama
Mingye-Lu

acrawl

by Mingye-Lu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to acrawl

No user-submitted related servers found.

    Related Servers

    • Scout

      klarlabs-studio
      A
      license
      Not graded
      quality
      A
      maintenance
      single-binary MCP server that gives AI agents a browser. 66 tools for navigation, form filling, data extraction, screenshots, and DOM diffing — built on pure Chrome DevTools Protocol.
      13
      MIT

    • BRYG

      flexiblepackage
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI assistants drive real Chromium browsers — navigate, click, type, read pages, run OCR, and record network traffic. 43 tools, credentials stay local, zero telemetry.
      -

    • Navigator MCP

      Sreehari2011
      A
      license
      B
      quality
      B
      maintenance
      Enables LLM agents to automate web browsers with token-efficient perception, stealth anti-detection, captcha solving, network interception, and isolated persistent sessions.
      51
      MIT

    • crw-mcp

      fastcrw
      A
      license
      A
      quality
      A
      maintenance
      Web scraping, crawling, and structured data extraction for AI agents. 5 tools: scrape (clean markdown from any URL), crawl (entire sites), map (discover URLs), extract (structured JSON), and search. 833ms avg latency, single binary, self-hostable.
      8
      1,133
      AGPL 3.0
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.8/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools have clearly distinct resource/action targets, and the list/inspect pairs for network, logs, and websockets are well separated. Minor overlap exists between click/click_at, wait/wait_for_scripts, and run_script/run_goal, but the descriptions make boundaries clear.

    Naming Consistency4/5

    Names are consistently snake_case and largely follow verb_noun or verb patterns such as list_*, inspect_*, save_*, and run_*. A few noun-only names like page_map, screenshot, and script_status are minor deviations, but the convention remains predictable.

    Tool Count2/5

    40 tools is a large surface for a browser automation server, and several tools form specialized list/inspect or low-level input pairs. Per the rubric, 25+ tools is considered too many for the apparent scope, even if many individual tools are justified.

    Completeness4/5

    Coverage spans navigation, interaction, extraction, network/log inspection, storage/cookies, performance, accessibility, coverage, and scripting. Minor gaps such as file upload, dialog handling, and setting cookies/storage prevent a perfect score, but core workflows are well covered.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources