/ 디렉터리 / 플레이그라운드 / web-scraper
● 커뮤니티 yfe404 ⚡ 바로 사용

web-scraper

제작: yfe404 · yfe404/web-scraper

Phased reconnaissance scraper that prefers APIs > sitemaps > HTML, picks the right Apify template (Cheerio vs Playwright), and only escalates anti-detection when signals warrant.

Intelligent web scraping via Claude Code. Runs a 5-phase reconnaissance (Phases 0–5) that tries the cheapest extraction path first: public APIs, sitemap feeds, structured data. Only when those fail does it consider browser automation, and only when protection signals appear does it layer on stealth. Built around TypeScript-first Apify Actor development, with templates (Cheerio for static, Playwright for JS-heavy).

왜 쓰나요

핵심 기능

라이브 데모

실제 사용 모습

web-scraper-skill.replay ▶ 준비됨
0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: web-scraper

Scrape a static listing site into a structured dataset

👤 Data engineers pulling public data (directories, price lists, public records) ⏱ ~45 min intermediate

언제 쓸까: You need a dataset from a public site that doesn't have an API.

흐름
  1. Let the skill do recon
    Use web-scraper. Target: https://example.com/listings. I want name + URL + category. Recon first — tell me the cheapest extraction path.✓ 복사됨
    → Skill reports: 'sitemap.xml available, use Cheerio'
  2. Scaffold the Apify Actor
    Scaffold a TypeScript Apify Cheerio actor for that extraction.✓ 복사됨
    → Actor tree + main.ts ready to run
  3. Run and iterate
    Run locally on 10 pages; tighten selectors if needed.✓ 복사됨
    → Clean JSON output

결과: An Apify Actor you can deploy for scheduled scrapes.

함정
  • Jumping to Playwright when Cheerio would do — Trust the recon — headful browsers 10x the cost unnecessarily
함께 쓰기: apify · filesystem

Discover and use a site's undocumented JSON API instead of HTML

👤 Scraper devs who want reliability ⏱ ~30 min intermediate

언제 쓸까: The page is a SPA and HTML is gross, but the XHR calls are clean JSON.

흐름
  1. Run API-discovery phase
    Use web-scraper phase 1 — API discovery on https://example.com/app. Enumerate XHR/fetch endpoints.✓ 복사됨
    → List of endpoints with observed payloads
  2. Build the JSON-based actor
    Generate an actor that hits those endpoints directly with auth as needed.✓ 복사됨
    → Lightweight fetch-based actor

결과: A far more stable scrape than HTML parsing.

함정
  • Private/session-auth APIs that break when token rotates — Plan token-refresh logic or fall back to browser flow

조합

다른 MCP와 조합해 10배 효율

web-scraper-skill + apify

Deploy the scaffolded actor to Apify for scheduled runs

Deploy this actor to my Apify account and schedule it daily.✓ 복사됨
web-scraper-skill + filesystem

Keep the actor code in-repo alongside the consuming app

Scaffold into scrapers/ and commit with the main project.✓ 복사됨

도구

이 MCP가 노출하는 것

도구입력언제 호출비용
recon url Always first 0
scaffold_actor template (cheerio|playwright), target After recon picks template 0
record_session url Debugging dynamic sites 0
run_local actor path, limit Iteration phase 0

비용 및 제한

운영 비용

API 쿼터
Apify has its own compute + proxy quotas
호출당 토큰
Moderate — scaffold and iteration loops
금액
Free skill; Apify costs separate
팁
Prefer Cheerio — one of the cheapest run profiles on Apify

보안

권한, 시크릿, 파급범위

최소 스코프: Apify API token with actor:read + actor:write
자격 증명 저장: APIFY_TOKEN in env
데이터 외부 송신: Whatever sites you target + Apify platform

문제 해결

자주 발생하는 오류와 해결

Cheerio returns empty selectors

Content is JS-rendered — rerun recon, expect Playwright template

Playwright times out

Bump navigation timeout; consider waiting for specific selector instead of networkidle

403 / bot-block page

Stop and reconsider. This is the legit signal to re-check ToS, not a cue to escalate stealth.

대안

web-scraper 다른 것과 비교

대안언제 쓰나단점/장점
Direct Apify consoleYou already know which template you needNo recon phase
firecrawlYou just need markdown of a page, not structured extractionNo actor scaffolding

더 보기

리소스

📖 GitHub에서 공식 README 읽기

🐙 열린 이슈 보기

🔍 400+ MCP 서버 및 Skills 전체 보기