Skip to main content
Glama

Related Servers

Alternatives to clawifi-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Unlimited web access MCP server for AI agents, enabling search, fetch, and learning across multiple sources while bypassing anti-bot protections.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables AI assistants to fetch web content in multiple formats (HTML, JSON, text, Markdown) with intelligent content extraction, chunk management, and browser automation support.
      6
      165 npm
      15
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP tool server that gives any AI agent the ability to search, scrape, and analyze content across the internet.
      42
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A custom MCP server that provides AI agents with tools to fetch web pages, extract readable article text, extract structured data by CSS selector, and check robots.txt permissions.
      MIT

    TDQS

    B3.4/5.0

    Scored across 14 tools

    Disambiguation3/5

    Three tools (fetch, scrape, extract) all retrieve content from a single URL, and only fine wording distinguishes 'Markdown of a page' from 'structured content' from 'schema-based extraction'. There is also dual async machinery (crawl/get_crawl vs create_job/get_job) plus an `estimate` tool that mirrors every other operation, so boundaries are described but easy to misselect.

    Naming Consistency3/5

    The set mixes consistent verb_noun names (get_crawl, create_job, get_job, map_site, list_history, list_monitors) with bare verbs (fetch, scrape, extract, crawl, estimate) and bare nouns (account, credits). It stays readable, but there is no single predictable pattern and polling is split between get_crawl and get_job.

    Tool Count5/5

    14 tools is comfortably within a healthy range and each maps to a plausible capability of a scraping/search API (search, fetch, scrape, extract, map, crawl, pricing, jobs, account, credits, history, monitors). Nothing is bloated enough to be unwieldy.

    Completeness4/5

    Core read/lifecycle workflows (search, fetch, scrape, extract, map, crawl, async jobs, cost estimation, billing, history) are well covered. Minor gaps: no cancel/delete for jobs or crawls, and list_monitors has no create/get counterpart, leaving monitor management a dead end; estimate also references a search_content operation not exposed as a tool.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues