Web Scraping MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | HasData API key, created free at https://app.hasdata.com |
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 |
|---|---|
| hasdata_web_scraping_web_scraping_scrapeWebPageA | Scrape Web Page Universal web scraper that fetches any public URL through managed proxies (datacenter or residential, geo-targeted) with optional JS rendering, custom headers, wait conditions, jsScenario actions (click, scroll, fill, waitFor), screenshots, resource/ad/URL blocking, and extractRules/aiExtractRules for LLM-driven structured extraction. Returns HTML, text, markdown, and/or JSON along with status code, extracted emails and links, CSS-selector extractions, and AI-structured fields per schema. Use as a fallback/universal fetcher for sites without a dedicated API, for scraping JS-heavy SPAs, bypassing bot protections, capturing screenshots, or producing clean markdown/structured JSON to feed downstream parsers, RAG pipelines, or data warehouses. |
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
There is only one tool in this server, so there is no possibility of confusing it with another tool. The purpose is clearly stated as a universal web scraper, making the surface unambiguous by definition.
With a single tool there is no cross-tool naming pattern to evaluate. However, the name itself mixes snake_case prefixes with a camelCase verb and repeats 'web_scraping', making it awkward and internally inconsistent.
A single tool for a domain as broad as web scraping feels thin, but the one tool is extremely feature-rich and can serve as a universal scraper. It is borderline rather than an extreme mismatch.
The tool covers the core web scraping workflow: fetching, rendering, extracting, screenshots, and structured output. It lacks explicit session/cache/scheduling management, but those can be worked around or handled externally.