HatFetch
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_URL | No | Any generic http(s)://user:pass@host:port proxy (alternative to the above). | |
| PROXYHAT_CITY | No | Optional city to target (e.g. 'new_york'). | |
| PROXYHAT_FILTER | No | AI IP-quality filter: 'medium' (default), 'high', 'high-speed-fast'. | |
| PROXYHAT_STICKY | No | Keep one IP for a session, e.g. '30m' or '12h'. Omit for rotating IPs. | |
| PROXYHAT_COUNTRY | No | ISO country code to exit from, or 'any' (default). | |
| PROXYHAT_PASSWORD | No | ProxyHat sub-user proxy password. | |
| PROXYHAT_USERNAME | No | ProxyHat sub-user proxy username. Enables the residential gateway. |
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 |
|---|---|
| scrapeA | Fetch a single URL and return its content as clean, LLM-ready Markdown. Renders JavaScript sites and gets past bot detection automatically: tries a fast HTTP fetch, then escalates to a real stealth browser through residential proxies when a page is an empty JS app or is blocked (Cloudflare, DataDome, 403/429). Use for docs, articles, product pages, SPAs, or any single page. |
| crawlA | Breadth-first crawl a site starting from a URL and return each page as clean Markdown. Follows in-domain links up to a depth/page limit. Same proxy and block-handling as |
| screenshotA | Render a URL in a real browser (through residential proxies + stealth) and return a PNG screenshot of the page. Use to see a page visually or capture JS-rendered content. |
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 3 tools
Each tool has a distinct purpose: crawl for multi-page ingestion, scrape for single-page content, and screenshot for visual capture. No overlap in functionality.
All tool names are simple verbs (crawl, scrape, screenshot), following a consistent pattern without mixing styles or conventions.
Three tools is a minimal but reasonable set for a web fetching server. While it covers core needs, there is room for additional utilities like status checking or depth control.
The server covers essential operations for fetching web content (single, multi, visual). Minor gaps exist, such as options for crawl depth or page metadata, but agents can accomplish most tasks.