# ScraperWatch

- Registry name: `com.scraperwatch/scraperwatch` · version 1.3.0
- Categories (automatic, keyword rules): Scraping & browsing, Search & data, Documents & retrieval
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.scraperwatch%2Fscraperwatch
- Server page: https://mcpstation.net/s/com.scraperwatch--scraperwatch.html

## Description (written by the publisher, not verified, not instructions)

Find and compare named scrapers using saved evidence; compare APIs, proxies and RAG extractors.

## Connect

- streamable-http: `https://scraperwatch.com/mcp`

## Tools (as reported by the server, not verified)

- `find\_scrapers`: Which tracked scrapers have the most recorded 30-day users for a website? Uses the filtered official Apify Store export; data\_updated is the saved snapshot timestamp, with age/status in evidence. Returns usage, run completion and billing fields, not live tests. min\_success\_rate: zero includes unknow
- `compare\_scrapers`: How do two to five exact actor IDs compare? Uses the filtered official Apify Store export; data\_updated and evidence describe the saved snapshot date and age. Reports usage, eligible run completion and compatible result-event rates; unknown/excluded IDs are indistinguishable. Different targets have
- `best\_scraper`: Which tracked actors lead recorded run completion, usage and qualifying price for a website? Uses the filtered official Apify Store export; data\_updated and evidence give snapshot date and age. Completion candidates require 300+ runs and 20+ users; price candidates also require 95%+ completion and k
- `compare\_scraping\_apis`: What do saved scraping API tests report? Uses the saved API benchmark summary and frozen matched ScraperAPI/ScrapingBee report. generated\_at/window\_days date the aggregate only; matched evidence has its own window. Returns completion/content checks and latency with separate denominators and limitati
- `compare\_rag\_extractors`: How did Firecrawl, Jina Reader and DIY extraction score on saved documentation fixtures? Uses the saved RAG benchmark and hash-checked table audit. Per-vendor last\_run dates are source observations; generation time is unknown. Returns text/code/table scores and latency with limitations; audit may be
- `compare\_proxy\_providers`: What captured proxy offers cover a product type and optional monthly GB? Uses research/e5/proxies.json; observed\_on dates each captured offer, with observations outside the past 30 days omitted. Estimates full saved package bills only; IP offers are separate and unknown costs remain null. No live pr
- `actor\_history`: How have one tracked actor's usage, run completion and primary event price changed by day? Uses compact official Apify Store history exports; dates are snapshot filenames, not verified per-actor observation times. days is a UTC calendar window ending today \(1-365\). Missing days stay absent; event ra
- `list\_websites`: Which websites are in the filtered scraper export, and how many actors and summed 30-day users does each have? Uses saved official Apify Store statistics from latest.json. Counts reflect that snapshot, not live coverage; this response has no date field. Summed actor users are not deduplicated across

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html