Find and compare named scrapers using saved evidence; compare APIs, proxies and RAG extractors.
Scored across 8 tools
best_scraper and find_scrapers both take a website and return leading tracked actors ranked by usage/run completion, making them hard to tell apart at selection time. The compare_* family (scrapers, scraping_apis, proxy_providers, rag_extractors) and list_websites are clearly distinct, so overlap is limited but real.
find_scrapers, list_websites, and the compare_* family follow a readable verb_noun pattern, but actor_history and best_scraper are noun-first and break the convention. The set is readable but mixes two naming styles.
Eight tools is a well-scoped size for a scraper-intelligence server, with each comparison target (scrapers, APIs, proxies, RAG extractors) earning its place. Slightly generous given the best_scraper/find_scrapers redundancy, but reasonable overall.
The surface covers discovery (list_websites, find_scrapers, best_scraper), per-actor history, and head-to-head comparisons across scrapers, scraping APIs, proxies, and RAG extractors — a coherent lifecycle for the domain. Minor gaps (no live-refresh or non-Apify source browsing) exist but agents can work around them.
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 rates are not total cost or necessarily per result.
Inputs: actor_id (required), days.
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 known result-event rates. No live tests or output-quality measure.
Inputs: site (required).
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 prices or performance measurements.
Inputs: product_type (required), monthly_gb.
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 unavailable or stale. No live tests or comparable cost.
Inputs: no named parameters.
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 no winner; listed rates are not total cost.
Inputs: actor_ids (required).
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 limitations; no current vendor requests.
Inputs: no named parameters.
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 unknown rates; positive thresholds require known rates.
Inputs: site (required), limit, min_success_rate.
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 actors.
Inputs: no named parameters. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Pages, crawls and URL batches as clean Markdown and JSON for AI agents, with an Evidence Record.
Comparison intelligence: live evidence from 20 sources, PESTLE/VS/Deep Research frameworks.
Scrape, map, crawl, search and monitor the web. Runs locally with no API key, cites every source.
Evidence-labeled Method search for AI Agents; optional contributor and Gateway discovery.
Add one secure layer between your agents and this server.