@trishchuk/mcp-fetch-server
Allows fetching content from websites protected by Akamai's bot detection systems by mimicking realistic browser TLS and HTTP/2 fingerprints.
Allows fetching content from websites protected by Cloudflare's anti-bot measures (Turnstile, Under Attack Mode) by impersonating real browser fingerprints.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@trishchuk/mcp-fetch-server fetch https://www.bbc.com using chrome_147 impersonation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@trishchuk/mcp-fetch-server
A high-performance Model Context Protocol (MCP) server providing an anti-bot-resilient fetch tool for AI agents (Claude Code, Claude Desktop, Cursor, Windsurf, Cline, Antigravity, etc.).
Powered by @trishchuk/fetch — a native curl-impersonate-style HTTP client that accurately mimics real browser TLS (JA3/JA4, ClientHello) and HTTP/2 fingerprints.
🚀 Why this server?
Standard Node.js/Undici HTTP clients get immediately flagged and blocked by modern bot-protection systems (Cloudflare Turnstile / Under Attack Mode, DataDome, PerimeterX / HUMAN, Akamai, Kasada, AWS WAF).
Furthermore, standard MCP fetching tools often fail on large payloads or blow up LLM token contexts.
@trishchuk/mcp-fetch-server solves both problems:
Realistic Browser Impersonation: Replicates exact cipher suites, TLS extensions, ALPN order, and HTTP/2 settings frames from modern browsers (Chrome, Safari, Firefox).
LLM Context-Safe Truncation: Streams and caps response bodies at 2MB (
maxResponseBytes). Oversized pages are cleanly truncated and flagged with"truncated": truerather than crashing with errors.Stateful Sessions: Maintain cookies, login states, and connection pools across multiple agent tool calls using the
sessionparameter.Smart Encoding: Automatically detects MIME types and returns clean UTF-8 text for HTML/JSON/XML or Base64 for binary files (images, PDFs, documents).
Related MCP server: SteadyFetch
✅ Requirements
Node.js >= 24 — required by
@trishchuk/fetch.Prebuilt native binaries ship for macOS (arm64, x64), Linux (x64/arm64, glibc and musl) and Windows (x64). Other platforms are not supported by the underlying client.
📦 Installation & Setup
Option 1: Run with npx (No installation needed)
You can run the server directly via npx:
npx -y @trishchuk/mcp-fetch-serverOption 2: Global or Local Installation
# Global
npm install -g @trishchuk/mcp-fetch-server
# Or clone & install locally
git clone https://github.com/x51xxx/mcp-fetch-server.git
cd mcp-fetch-server
npm install⚙️ MCP Client Configuration
Claude Code
Add directly via CLI:
# Using npx (recommended)
claude mcp add fetch -- npx -y @trishchuk/mcp-fetch-server
# Or using local path
claude mcp add fetch -- node /path/to/mcp-fetch-server/src/index.jsClaude Desktop
Add to your claude_desktop_config.json:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
{
"mcpServers": {
"fetch": {
"command": "npx",
"args": ["-y", "@trishchuk/mcp-fetch-server"]
}
}
}Cursor / Windsurf / Antigravity (.mcp.json)
Create or update .mcp.json in your workspace:
{
"mcpServers": {
"fetch": {
"command": "npx",
"args": ["-y", "@trishchuk/mcp-fetch-server"]
}
}
}🛠️ Tool Reference: fetch
Input Parameters
Parameter | Type | Default | Description |
|
| required | Target absolute URL (e.g. |
|
|
| HTTP method ( |
|
|
| Request headers as key-value pairs ( |
|
|
| Request body sent as UTF-8 string (JSON, form-encoded, raw text). |
|
|
| Browser fingerprint preset (e.g. |
|
|
| Declared OS: |
|
|
| Proxy URL: |
|
|
| Session ID for sharing client connections and cookie jars across multiple calls. |
|
|
| Custom DNS pinning (e.g. |
|
|
| Redirect mode: |
|
|
| Force protocol version: |
|
|
| Minimum TLS version: |
|
|
| Maximum TLS version: |
|
|
| Overall request timeout in milliseconds. |
|
|
| Body limit in bytes (max 2MB). Responses exceeding this are safely truncated. |
|
|
| Body return format: |
Response Schemas
1. Successful HTTP Exchange
Any completed HTTP transfer returns a standard JSON result (including 404, 500, or 3xx under redirect: "manual"):
{
"status": 200,
"statusText": "OK",
"ok": true,
"url": "https://example.com/data",
"redirected": false,
"headers": {
"content-type": "application/json; charset=utf-8",
"cache-control": "max-age=3600"
},
"bodyEncoding": "text",
"body": "{\"message\": \"Hello world\"}",
"truncated": false
}2. Network / Transport Failure
If the network connection fails, times out, or the URL is invalid, the tool returns isError: true:
{
"error": true,
"code": "TIMEOUT",
"message": "failed to read response body: request or response body error: operation timed out"
}💡 Usage Examples for Agents
1. Bypass Bot Detection on Protected Target
{
"url": "https://protected-site.com/products",
"impersonate": "chrome_147",
"platform": "macos",
"headers": {
"Accept-Language": "en-US,en;q=0.9"
}
}2. Multi-Step Scraping with Persistent Session (Cookie Jar)
// Step 1: Login / Obtain Session Cookie
{
"url": "https://example.com/api/login",
"method": "POST",
"session": "agent-crawler-01",
"headers": { "Content-Type": "application/json" },
"body": "{\"user\":\"admin\",\"password\":\"secret\"}"
}
// Step 2: Access protected resource (session cookies automatically preserved)
{
"url": "https://example.com/api/dashboard",
"session": "agent-crawler-01"
}3. Route Through a SOCKS5 Proxy
{
"url": "https://geo-restricted.example.com",
"proxy": "socks5://user:pass@proxy.example.com:1080",
"impersonate": "safari_26"
}4. Fetching Binary Assets (Images, PDFs)
{
"url": "https://example.com/report.pdf",
"encoding": "base64"
}5. DNS Pinning for SSRF-Safe Ingestion
{
"url": "https://internal-origin.example.com/feed",
"resolve": {
"internal-origin.example.com": "192.0.2.42"
},
"redirect": "manual"
}🔬 Impersonation Presets & Fingerprints
@trishchuk/mcp-fetch-server supports a wide range of browser fingerprints:
Chrome:
"chrome_100"…"chrome_149"(e.g."chrome_147","chrome_131","chrome_116")Edge:
"edge_101"…"edge_148"Opera:
"opera_116"…"opera_131"Firefox:
"firefox_109","firefox_133","firefox_147"…, plus"firefox_private_136"and"firefox_android_135"Safari:
"safari_15.3"…"safari_26.4", plus iOS/iPad variants ("safari_ios_26","safari_ipad_26")OkHttp (Android apps):
"okhttp_3.9"…"okhttp_5"Dynamic:
"random","weighted_random"(rotates fingerprints automatically, pinned persession)
Version numbers use underscores (chrome_147, not chrome147). An unknown name fails fast with an
InvalidArg error that lists every accepted variant.
🧪 Development
npm install
npm start # run the server over stdio
npm test # end-to-end smoke tests, no network required
npm run format # format with Biome
npm run lint # lint with Biome
npm run check # format + lint check, also run before publishThe tests spawn the real server over stdio and drive it with an MCP client against a local HTTP server,
covering truncation at the cap, redirect modes, HEAD, base64 bodies, timeouts and transport errors.
📄 License
MIT © Taras Trishchuk
Available Tools
1 toolfetchFetchA
HTTP fetch backed by @trishchuk/fetch: a curl-impersonate-style client that emulates a real browser TLS/HTTP2 fingerprint (JA3/JA4, ClientHello, ALPN) so requests are not flagged by fingerprint-based bot detection (Cloudflare, DataDome, PerimeterX, etc.) the way Node's default HTTP client is. Use it for GET/POST/etc. against sites that block or challenge plain scrapers.
Inputs: url (required), body, proxy, method, +12 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion with other tools. The tool's purpose is clearly described and distinct by default.
With only one tool, there is no pattern to judge. The name 'fetch' is simple and conventional, matching common HTTP client terminology, but the lack of a verb_noun convention is neutral.
A single tool for an HTTP fetch server is too minimal. Most similar servers would include additional tools for managing headers, cookies, or caching, making this feel under-scoped for its stated purpose of scraping.
The server only provides a basic fetch tool with no support for managing sessions, handling redirects, managing cookies, or performing other common HTTP operations. This leaves significant gaps for any realistic scraping workflow.
Maintenance
Related MCP Connectors
Reliable web fetching for AI agents with retry, circuit breaker, caching, and anti-bot bypass
Reliable web access for AI agents: smart HTTP, rotating proxies, and full-browser rendering.
Isolated, fingerprint-protected browser profiles for AI agents: one per task, with its own proxy
Fetch web pages and APIs past anti-bot walls, with reusable browser sessions.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to perform undetectable browser automation that bypasses Cloudflare, antibots, and social media blocks. Provides 105 tools for element extraction, network debugging, and real-world web scraping with a 98.7% success rate on protected sites.170 PyPI3,382MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with reliable web fetching capabilities, handling retries, caching, and anti-bot bypass automatically.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to perform stealth browser automation and anti-detection web interaction, including session management, humanized interactions, and bypassing anti-bot/WAF protections.MIT
- AlicenseBqualityCmaintenanceEnables LLM agents to automate web browsers with token-efficient perception, stealth anti-detection, captcha solving, network interception, and isolated persistent sessions.51MIT