Stealth Web Scraper MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRAPER_HOST | No | HTTP bind address | 127.0.0.1 |
| SCRAPER_PORT | No | HTTP bind port | 8080 |
| SCRAPER_API_KEY | No | Require a bearer token on HTTP | |
| SCRAPER_CACHE_TTL | No | Default cache freshness in seconds | 3600 |
| SCRAPER_PROXY_URL | No | Residential proxy, used only after a direct fetch is blocked | |
| SCRAPER_MAX_RETRIES | No | Request retries | 2 |
| SCRAPER_FETCH_TIMEOUT | No | Request timeout | 20 |
| SCRAPER_BROWSER_LOCALE | No | Browser locale; keep consistent with your proxy's location | en-US |
| SCRAPER_BROWSER_CHANNEL | No | Browser to launch; empty for bundled Chromium | chrome |
| SCRAPER_BROWSER_HEADLESS | No | false runs a visible, harder-to-detect browser | true |
| SCRAPER_BROWSER_TIMEZONE | No | Browser timezone; keep consistent with your proxy's location | system |
| SCRAPER_CACHE_MAX_ENTRIES | No | Cache size | 256 |
| SCRAPER_ALLOW_PRIVATE_NETWORKS | No | Allow localhost and private IPs | false |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_url_stealthA | Fetch a web page and return its main content as clean Markdown. Pass query to get only the passages that answer a question. Handles JavaScript-rendered and bot-protected pages by falling back to a real Chrome browser. Results are cached; long pages are paginated with offset/next_offset. |
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 1 tool
With a single tool there is no possibility of selection confusion; an agent cannot mistake scrape_url_stealth for anything else. The description clearly scopes the tool's behavior (query filtering, JS fallback, caching, pagination).
The lone name scrape_url_stealth follows a clear verb_noun_modifier snake_case pattern. No competing conventions exist to create inconsistency.
One tool is thin for a server branded as a scraper platform, even though that tool is genuinely capable. It lands in the borderline zone where a single entry point handles everything but leaves no room for distinct capabilities.
Core single-page fetch, JS rendering, caching, and pagination are covered, but common scraping needs are absent: batch/multi-URL fetch, crawling, sitemap/robots handling, and structured or raw HTML output modes. Agents can work around these, but the surface is not fully complete for the stated domain.