No user-submitted related servers found.
Scored across 39 tools
The families (scrape/crawl/batch/monitor/delivery/login) are clearly separated and descriptions explicitly add 'Not for:' clauses and cross-references, which resolves most confusion. The main friction points are near-neighbours like scrape vs batch_scrape vs scrape_product, batch_products vs batch_scrape, and preview_monitor vs get_monitor_run, which require reading the full text to separate.
Nearly everything follows a verb_noun pattern (get_scrape, cancel_crawl, list_monitors, pause_delivery_destination), and the crawl_/batch_/monitor_/delivery_ families are predictable. Deviations are modest: bare verbs (scrape, map) and the noun_verb ordering of batch_scrape/batch_products break the pattern for two prominent tools.
39 tools is heavy, but the server genuinely spans several subdomains (scrape, map, crawl, batch, product extraction, monitors, webhook deliveries, saved logins), so much of the count is earned. Still, the surface feels over-granular in places, e.g. mirrored pause/resume pairs for both monitors and delivery destinations plus separate get/list/errors variants per job type.
Lifecycle coverage is strong: read (scrape/get_scrape), discover (map), bulk (batch_*), crawl (start/wait/get/errors/cancel/resume), monitors (create/run/pause/resume/get_run), deliveries (create/pause/resume/list/retry) and saved logins (import/list/remove). Gaps are minor: no update/delete for monitors, no delete/update for delivery destinations, and no explicit way to purge retained results.