clawifi-mcp
Related Servers
Alternatives to clawifi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceUnlimited web access MCP server for AI agents, enabling search, fetch, and learning across multiple sources while bypassing anti-bot protections.MIT
- AlicenseAqualityBmaintenanceAn 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.6165 npm15MIT
- AlicenseNot gradedqualityCmaintenanceMCP tool server that gives any AI agent the ability to search, scrape, and analyze content across the internet.42MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to search the web and extract clean Markdown content, with support for JavaScript rendering, structured data extraction, and screenshots.2-
- AlicenseNot gradedqualityDmaintenanceA 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
Scored across 14 tools
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.
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.
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.
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.