Scrape-LE
Check whether a page is actually scrapeable before you burn hours debugging.
What Scrape-LE does
Whether a page can be scraped is a question best answered before the scraper is written. Scrape-LE loads a URL in a real headless Chromium and reports what it found: HTTP status, page title, load time, console errors, a full-page screenshot, and four detections covering anti-bot measures, authentication requirements, rate limiting and robots.txt rules.
What people use it for
Before you write the scraper
Find out whether a page is reachable, gated or defended — before the work, not after.
Real browser, real answer
The page loads in headless Chromium, so client-rendered content and bot checks behave as they actually will.
Respect robots.txt
The origin rules are fetched and reported alongside everything else. A scrapeability report is information, not permission.
Install Scrape-LE
VS Code
ext install nolindnaidoo.scrape-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.scrape-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
ZedComing soon
npx -y scrape-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and analyze_robots_txt appears in its tool list. The one-click listing in Zed's extension registry is a pull request awaiting review. Track the review.
AI agents
npx -y scrape-le-mcpRuns Scrape-LE's engine as an MCP server, so an agent can call analyze_robots_txt with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where Scrape-LE lives
- VS Code Marketplacescrape-le
- Open VSXfor Cursor and VSCodium
- GitHubsource, issues, changelog
- npmscrape-le-mcp
- MCP registryio.github.nolindnaidoo/scrape-le
The other nine
Extract string values from JSON, YAML, CSV, TOML, INI, and .env — for i18n.
Extract numeric values from JSON, YAML, CSV, TOML, INI, and .env.
Pull every file path out of JS/TS imports, JSON, HTML, CSS, TOML, CSV, and .env files.
Extract and analyze colors from CSS, SCSS, LESS, Stylus, HTML, JS/TS, and SVG.
Extract URLs from documentation, configs, and code.
Extract date and time data from logs, configs, and code.
Find, test, and validate the regular expressions in any file — match reports and built-in ReDoS screening.
Detect and sanitize credentials, tokens, API keys, and private keys locally — before you commit.
Spot missing keys across your .env files — automatic checks, a status bar counter, and a markdown report.