ScrapeUnblocker MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRAPEUNBLOCKER_KEY | Yes | Your ScrapeUnblocker API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_htmlA | Fetch the fully rendered HTML of any web page through ScrapeUnblocker, bypassing anti-bot protection (Cloudflare, DataDome, PerimeterX, Akamai, Shape). Use this when a normal fetch is blocked (403/429, captcha, 'access denied') or when the page needs a real browser to render. Returns the raw HTML as text. For pages that need interaction (accept a cookie banner, click a tab, type into a search box, scroll to trigger lazy loading) pass |
| list_elementsA | Load a page through ScrapeUnblocker and return a JSON list of its notable elements (links, inputs, buttons, selects, etc.) with a ready-to-use |
| fetch_parsedA | Fetch a web page through ScrapeUnblocker and return AI-parsed structured JSON instead of raw HTML (e.g. product details, article content). Best for extracting fields from product, listing or article pages without writing your own HTML parsing. If the page holds no structured data, the result says so (that call is not billed) - use fetch_html for the page itself. |
| google_searchA | Run a Google search through ScrapeUnblocker and return the organic results as structured JSON. Use this to discover URLs before fetching them. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct action: fetch_html (raw HTML), fetch_parsed (structured JSON), google_search (URL discovery), and list_elements (read-only selector discovery). The descriptions explicitly cross-reference each other (e.g. 'use fetch_html for the page itself'), making selection unambiguous.
All four names are snake_case and follow a verb_noun pattern (fetch_html, fetch_parsed, list_elements, google_search). The convention is uniform and predictable.
Four tools is lean and each earns its place for a scraping service, covering fetch, parse, search, and element discovery. It sits at the low end of the ideal range but is well-scoped rather than thin.
The surface covers the core scraping lifecycle: discovery (google_search), selector inspection (list_elements), raw fetch, and parsed extraction with interactive steps. Minor gaps like multi-page crawling or pagination/session handling exist but core workflows are covered.