No user-submitted related servers found.
Scored across 7 tools
Most tools have clearly distinct roles: map for discovery, scrape for one-shot fetches, and the async trio (scrape_async/scrape_status/scrape_result) split cleanly by submit/poll/fetch. The main overlap is scrape vs scrape_async, which both extract page content; the descriptions explicitly steer toward sync for quick fetches and async for long jobs, but an agent could still misselect. whoami and usage are related (account/credits) yet distinguishable.
All names are lowercase snake_case, which is consistent. There is a minor convention mismatch within the scrape family: scrape_async is verb-first while scrape_status and scrape_result are noun-first, but each name remains immediately readable and grouped by the 'scrape' prefix. map, whoami and usage are single-word outliers but recognizable.
Seven tools is well-scoped for a scraping API wrapper: four cover the scrape lifecycle (sync, async submit, status, result), one for discovery, and two for account/billing introspection. No tool feels redundant or missing at the count level.
The core lifecycle is covered: site discovery via map, sync and async scraping, polling and result retrieval, plus auth and usage checks. Minor gaps exist — no cancel/abort for async jobs, no job listing, and no recursive multi-page crawl beyond map+scrape — but these are workable for typical agent workflows.
