ScraperWatch

com.scraperwatch由 scraperwatch.com 发布官方发布者v1.3.0更新于 Oct 24, 2026

使用已保存的证据查找并比较具名抓取工具;比较API、代理和RAG提取器。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

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

已验证Streamable HTTP可网页运行知识与记忆

概览

ScraperWatch 的托管 MCP 服务(scraperwatch.com),由 scraperwatch.com 发布;无需登录;Streamable HTTP;8 个工具。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

发布者
scraperwatch.com
端点
scraperwatch.com
最近检查

安装

在 SourceWeft 中

  1. 打开 控制台中的 ScraperWatch,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.scraperwatch%2Fscraperwatch/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "scraperwatch": {
      "type": "http",
      "url": "https://scraperwatch.com/mcp"
    }
  }
}

工具

8

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 unknown rates; positive thresholds require known rates.

输入参数site必填limitmin_success_rate

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 no winner; listed rates are not total cost.

输入参数actor_ids必填

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 known result-event rates. No live tests or output-quality measure.

输入参数site必填

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 limitations; no current vendor requests.

无需输入参数。

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 unavailable or stale. No live tests or comparable cost.

无需输入参数。

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 prices or performance measurements.

输入参数monthly_gbproduct_type必填

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 rates are not total cost or necessarily per result.

输入参数daysactor_id必填

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 actors.

无需输入参数。

版本历史

4
  1. v1.3.0最新Oct 21, 2026
  2. v1.2.0Oct 19, 2026
  3. v1.1.0Oct 19, 2026
  4. v1.0.0Oct 18, 2026

评分

已满足适用检查项的 72%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分

    请在注册中心条目中发布图标。

  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。