Skip to main content
Glama
AIMLPM

AIMLPM/markcrawl

by AIMLPM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AIMLPM/markcrawl

  • firecrawl-mcp-server

    firecrawl
    A
    license
    A
    quality
    C
    maintenance
    A Model Context Protocol (MCP) server implementation that integrates with FireCrawl for advanced web scraping capabilities.
    26
    22,552 npm
    7,510
    MIT

Related Servers

  • icecrawl MCP server

    MrGreenlaw
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables scraping single pages or crawling entire websites, converting content to markdown and optionally extracting structured data with Claude.
    -
  • HatFetch by ProxyHatCom

    HatFetchofficial

    ProxyHatCom
    A
    license
    A
    quality
    A
    maintenance
    Enables LLM agents to read any website by scraping and crawling into clean Markdown, automatically bypassing bot detection with residential proxies.
    2
    3
    30 npm
    MIT

  • Gnosis-markdown

    SHCV-it
    A
    license
    Not graded
    quality
    A
    maintenance
    Fetch web pages into clean, RAG-ready Markdown with a verifiable provenance record — source URL, UTC fetch time, SHA-256 of the response body, redirect chain, and an extraction-fidelity metric. Writes WARC archives and honours robots.txt/ai.txt, so every document an agent reads can be re-verified and cited.
    141 PyPI
    2
    MIT

  • Crawlberg MCP Server

    xberg-io
    A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to crawl and scrape websites, converting HTML to clean Markdown and structured metadata with support for JavaScript rendering, bot evasion, and SSRF protection.
    178
    MIT
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

A4.7/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct role in the crawl pipeline: crawl_site fetches content, list_pages provides an overview, search_pages filters by keyword, read_page returns full content, and extract_data produces structured fields. There is no overlap or ambiguity between the tools.

Naming Consistency5/5

All tool names follow the same verb_noun snake_case pattern: crawl_site, list_pages, search_pages, read_page, extract_data. The verbs are consistent and clearly describe the operation, and the nouns reflect the target object.

Tool Count5/5

The server has 5 tools, which is well-scoped for its purpose. Each tool is necessary for the crawl, browse, and extract workflow, and there is no superfluous or redundant surface area.

Completeness5/5

The tool set covers the full lifecycle of crawling and working with web content: ingestion (crawl_site), discovery (list_pages, search_pages), retrieval (read_page), and structured analysis (extract_data). There are no obvious dead ends or missing operations for the stated domain.

Maintenance

ActivityInactive
ResponsivenessResponsive

Resources