alterlab-mcp-server
Related Servers
Alternatives to alterlab-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables web scraping and document processing with JavaScript execution, anti-detection measures, batch processing, and structured data extraction. Supports multiple formats including markdown, HTML, screenshots, and handles PDFs with OCR capabilities.4MIT
- AlicenseNot gradedqualityFmaintenanceEnables intelligent web scraping with support for static pages, JavaScript-rendered SPAs, and natural language data extraction.MIT
- AlicenseNot gradedqualityBmaintenanceEnables headless-Chromium web automation, including rendering fully-executed HTML, extracting structured data with CSS selectors, capturing screenshots, and AI-assisted smart scraping of web pages.292 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables fetching, crawling, and browsing anti-bot protected web pages with real browser rendering, returning clean JSON or markdown, and solving captchas.-
- AlicenseAqualityBmaintenanceEnables web scraping and data extraction from websites with geographic flexibility, privacy features, and anti-detection capabilities. Supports scraping general websites, Google Search, Amazon Search, and Reddit with customizable parameters for rendering, geolocation, and locale.33729 npm39ISC
- AlicenseAqualityCmaintenanceEnables crawling websites, including JavaScript-rendered pages, and returns extracted page content as JSON with structured error reporting.1MIT
TDQS
Scored across 26 tools
Most tools have clearly distinct purposes and descriptions proactively cross-reference each other (scrape vs batch_scrape vs batch vs crawl vs map, with URL-count thresholds spelled out; batch_status vs get_job explained). A few pairs remain genuinely confusable: update_session vs refresh_session both rotate cookies, list_beta_features vs list_my_beta_features differ only subtly, and check_balance vs get_usage both report balance/spend.
All tools share the alterlab_ prefix and are snake_case, which is highly predictable. However the core operations use bare verbs (scrape, crawl, map, search, batch, screenshot) while everything else is verb_noun (get_job, check_balance, create_session), a minor internal inconsistency rather than a real problem.
26 tools is at the upper edge and a bit heavy for one server, spread across four sub-domains: fetching (scrape/batch/crawl/map/search/screenshot/extract), job polling, session management, and beta-feature/account admin. Each tool is defensible, but the beta-feature group and the balance/usage pair feel like peripheral surface that inflates the set.
The fetching lifecycle is well covered: single, small batch, large async batch with status, crawl with status and cancel, plus map, search, screenshot, extract, and cost estimation. Gaps are modest: batch has status but no cancel or listing equivalent to crawl_cancel, and async job handling only offers get_job with no enumeration.