Skip to main content
Glama
Crawleo

crawleo-mcp

by Crawleo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to crawleo-mcp

Related Servers

  • webscout-mcp

    wxs-lang
    A
    license
    A
    quality
    A
    maintenance
    Enables AI agents to perform web searches, fetch and extract page content, and crawl sites with caching, rate limiting, and robots.txt compliance, all without needing API keys.
    11
    520 PyPI
    1
    MIT

  • GroundRoute

    PROJECT-B-26
    A
    license
    A
    quality
    D
    maintenance
    Web search for AI agents across 6 engines (Serper, Brave, Exa, Tavily, Firecrawl, Perplexity) through one search tool. Routes each query to the cheapest engine that clears a quality bar and caches repeats. Hosted, streamable-HTTP, BYOK supported.
    1
    1
    MIT

  • WaterCrawl MCP

    watercrawl
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides AI systems with web crawling, scraping, and search capabilities through WaterCrawl's API, enabling content extraction, site mapping, and web search with customizable options.
    2 npm
    8
    ISC
  • OpenSERP Cloud by openserpapi

    OpenSERP Cloudofficial

    openserpapi
    A
    license
    B
    quality
    C
    maintenance
    Search API for AI, SEO & automation. Browser-rendered Google, Bing, Yandex, Baidu, DuckDuckGo and Ecosia results with URL extraction (+image search and engine metadata tools)
    9
    53 npm
    2
    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,069
    AGPL 3.0
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: crawl_web targets a specific webpage for content extraction, while search_web performs broader web searches. There is no overlap in functionality, making it easy for an agent to choose the correct tool based on the need for focused crawling versus exploratory searching.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (crawl_web, search_web) with clear, descriptive names that align with their functions. The naming is uniform and predictable, using snake_case throughout without any deviations.

Tool Count2/5

With only two tools, the server feels under-scoped for a web crawling and search domain. While the tools cover basic operations, the lack of additional tools (e.g., for managing crawl sessions, filtering results, or handling errors) limits functionality and may require agents to work around gaps in more complex workflows.

Completeness2/5

The tool surface is severely incomplete for a web crawling and search server. There are no tools for operations like configuring crawl parameters, managing search history, handling authentication, or processing batch requests, which are common in such domains. This will likely cause agent failures in extended or nuanced tasks.

Resources