chrome-mcp-web-fallback

Retry failed web retrievals once with chrome-mcp and return both outcomes.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/droxey/skills --skill chrome-mcp-web-fallback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-mcp-web-fallback
Source: https://github.com/droxey/skills/tree/main/chrome-mcp-web-fallback
Command: npx skills add https://github.com/droxey/skills --skill chrome-mcp-web-fallback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses web retrieval failures caused by blocking, dynamic rendering, bot protection, redirects, transport errors, or other non-browser HTTP limitations by retrying once via a browser-driven path.

Core Features & Use Cases

  • Failure-aware retry flow: Captures a one-line symptom from the initial attempt (HTTP status, timeout/TLS/DNS/connection errors, bot interstitials, or consent/login redirects).
  • Scoped chrome-mcp extraction: Re-opens the same target with chrome-mcp, waits for the page to settle, and extracts only what the user’s request needs.
  • Traceable dual outcome: Returns both initial_attempt (tool + failure symptom) and fallback_attempt (chrome-mcp + extracted result or failure), then stops to prevent loops.
  • Use case: Validate and scrape data from a website where curl/fetch works inconsistently, such as when a page intermittently returns 403/429 or requires client-side rendering.

Quick Start

Use the chrome-mcp-web-fallback skill when a direct web request to your target URL fails due to blocking or dynamic rendering, and ask it to extract the specific data you need from that page.

Frequently Asked Questions about chrome-mcp-web-fallback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scrape website data when my requests get blocked by HTTP 403 or bot protection?

Scraping blocked website data requires a fallback retry mechanism using browser automation to bypass HTTP 403 errors and bot protection. This Skill recovers failed fetches by capturing the initial failure symptom and retrying the extraction once via a browser-driven path.

What's the best way to retrieve dynamically rendered web content when curl or fetch fails?

Retrieving dynamically rendered web content requires waiting for the page to settle in a real browser environment. This Skill uses chrome-mcp to re-open the target URL, execute client-side rendering, and extract the specific data requested after non-browser tools fail.

Can I use chrome-mcp to recover web retrieval tasks that fail due to TLS or DNS errors?

You can use chrome-mcp to recover web retrieval tasks failing from transport errors like TLS, DNS, or timeouts. The Skill captures the specific connection failure symptom and performs a single browser-driven retry to fetch the targeted content.

Does this browser fallback approach prevent infinite retry loops during scraping validation?

This browser fallback approach prevents infinite retry loops by stopping after a single chrome-mcp extraction attempt. It returns a traceable dual outcome containing both the initial failure symptom and the fallback result, then halts to ensure scraping validation workflows remain stable.

How do I extract specific data from a URL that intermittently returns 429 status codes?

Extracting specific data from URLs returning intermittent 429 status codes requires scoping a browser-driven retry to the user's exact request. This Skill re-opens the target with chrome-mcp, waits for the page to settle, and extracts only the data needed instead of the full page.

Why does my direct web request fail on pages with consent or login redirects?

Direct web requests fail on consent or login redirects because non-browser HTTP tools cannot handle client-side interstitials. This Skill identifies the redirect symptom from the initial attempt and retries the URL with chrome-mcp to navigate past the redirect and extract the target content.