ShardX Launcher | ProxyshardDoc

ShardX Browser is an anti-detect browser that allows you to create profiles with unique fingerprints, associate each profile with a proxy, and manage dozens of accounts as different individuals on different devices. In addition to manual mode, it offers a local automation API for Puppeteer/Playwright.

Key Features:

• Generates unique fingerprints for Windows, macOS, and Linux (navigator, screen, client hints, WebGL/WebGPU, etc.).

• Noise injection for individual vectors: canvas, WebGL, audio, client rects, fonts, sensors.

• Unlimited profiles with folder organization.

• Proxy binding to profiles (SOCKS5/HTTP/HTTPS) with auto-testing upon addition.

• Local HTTP API for complete automation.

• Chrome DevTools Protocol (CDP) management - Puppeteer, Playwright, and similar tools.

• Export and import cookies between profiles.

• Separate MCP server for AI agent management.

Fingerprints and Anti-Detect:

For each profile, ShardX substitutes a consistent set of parameters: User-Agent, platform, CPU cores, RAM (never exceeding the host's), screen resolution, Sec-CH-UA, and more. Noise is applied to individual vectors like canvas, WebGL, audio, client rects, fonts, and sensors. Each noise block can be enabled independently, ensuring profile fingerprints are stable within sessions but differ from other profiles and your actual device. Fingerprints are unique and not tied to hardware. CPU cores and RAM are adjusted to the host and not inflated, and the screen is cropped to the real display, reducing detection risks from inconsistencies.

Proxies, QUIC, and WebRTC:

ShardX integrates seamlessly with our proxies. Upon each profile launch, before the browser starts, the assigned proxy is live-checked for UDP-relay support (SOCKS5 UDP_ASSOCIATE). If UDP is functional, QUIC is enabled, and WebRTC traffic routes through the proxied UDP-relay. If UDP is unavailable, QUIC is disabled, and WebRTC is forced into TCP-only mode to prevent real IP leaks. Timezone, locale, and geolocation fields in auto mode are also dynamically fetched via the proxy at launch. The combination of ShardX and our UDP-supporting proxies effectively closes WebRTC leaks at the browser level, as UDP traffic flows through the proxy instead of directly from your IP.

Automation: Local API

A local HTTP server is launched within the application on 127.0.0.1 (default port 40325, configurable in Settings → Automation API). This server is inaccessible from outside your machine. All requests, except GET /health, require a Bearer token (a persistent JWT from settings). The Regenerate token button in settings instantly changes the secret, with the new token working immediately and all old tokens becoming invalid. A typical automation scenario involves getting a new unique fingerprint, optionally adjusting it, creating a profile with the fingerprint and proxy, and then starting/stopping the profile via the API. Temporary profiles can be created with the `temporary` flag, hidden from the interface, and automatically deleted after the browser closes.

MCP Server for AI Agents:

The package includes a separate MCP server (Model Context Protocol) that allows an AI client to manage the launcher via the same API and the profile's browser via CDP. This is a separate Node process, not part of the HTTP API. It can be downloaded directly from the launcher (Settings → MCP server → Download MCP server). Configuration is done via two variables: SHARDX_API (base API URL) and SHARDX_TOKEN (the Bearer token). The MCP server provides API tools (wrappers for launcher methods) and browser tools over CDP (navigation, JS execution, screenshots, clicks, text input, tab management, and waits). CDP (remote-debugging) is only enabled when launching a profile via the API; launches from the interface do not have a debug port to maintain anti-detect integrity.