A
licenseA
qualityC
maintenanceA Model Context Protocol (MCP) server implementation that integrates with Firecrawl for advanced web scraping capabilities.
26
129,393 npm
7,617
MIT
AIMLPM/markcrawl
by AIMLPM
Related Servers
Alternatives to AIMLPM/markcrawl
Related Servers
- FlicenseNot gradedqualityCmaintenanceCrawl entire websites, sitemaps, and documentation portals into clean, LLM-ready Markdown without ads, cookie popups, or noise for RAG pipelines and AI agents.-
- FlicenseNot gradedqualityDmaintenanceEnables scraping single pages or crawling entire websites, converting content to markdown and optionally extracting structured data with Claude.-
- AlicenseNot gradedqualityCmaintenanceEnables converting any URL or website into clean, LLM-ready Markdown, supporting single-page scraping and full-site crawling for AI agents.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and LLM pipelines to fetch webpages or crawl sites, extract main content, and convert it to clean, token-efficient Markdown with preserved links. It supports configurable crawling depth, caching, robots.txt compliance, and optional chunking for downstream processing.-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and LLM pipelines to fetch and crawl websites locally, extract readable content, and convert pages into clean Markdown with preserved links while minimizing token usage.-
HatFetchofficial
AlicenseAqualityCmaintenanceEnables LLM agents to read any website by scraping and crawling into clean Markdown, automatically bypassing bot detection with residential proxies.328 npmMIT
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
ResponsivenessNo issues