TLS Handshake Analyzer / Bypass — MCP
Detects Akamai WAF/CDN fingerprinting signals and helps compare browser-grade TLS/HTTP2 profiles to determine whether Akamai is blocking requests based on JA3/JA4, header order, or HTTP/2 fingerprint.
Detects Cloudflare WAF/CDN signals such as cf-ray and cf-mitigated and helps test browser-grade TLS/HTTP2 fingerprint bypass against Cloudflare-protected endpoints.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
TLS Handshake Analyzer / Bypass — MCP
Browserless Multi-Engine TLS/HTTP2 Fingerprint Bypass & Handshake Analyzer, X.509 Diagnostics & Stateful Sessions for AI Agents (MCP), CLI, Python & FastAPI
Why This Exists • Live Proof • Engines • What You Can Do • MCP Setup • CLI Examples • REST API
Why This Exists
Standard HTTP tools and fetch MCP servers (requests, httpx, urllib, Node fetch) use default system OpenSSL handshakes. Modern anti-bot/WAF layers inspect the TLS ClientHello (JA3 / JA4), HTTP/2 Akamai fingerprint (SETTINGS, WINDOW_UPDATE, pseudo-header order), and header order — immediately returning 403 before your request even touches application logic.
TLS Handshake Analyzer gives AI models (via MCP) and developers a lightweight, browserless way to:
Speak real browser TLS/HTTP2/HTTP3 across 3 independent browser-grade C/Rust/Go stacks (without launching Playwright/Chromium)
Prove whether a target blocks on TLS vs credentials by contrasting against a Python OpenSSL baseline
Inspect raw TLS handshakes, timings, ALPN, cipher negotiation & X.509 chains (even on expired or self-signed certs)
Run stateful multi-step flows (
init→login→ authenticated API calls) with persistent cookie jars and pinned TLS statePull unfiltered full dumps (
full_dump=True) — every header, duplicateSet-Cookie, redirect hop, unlimited response body, and peer certificates
Common Use Cases
Use Case | Why Use This Tool |
AI-Agent Browserless Web Scraping | Stop getting |
Authenticated Logins & Session Workflows | Sign in to your own accounts or private APIs multi-step ( |
TLS Fingerprint / Anti-Bot Debugging | Compare |
Certificate & Protocol Auditing | Diagnose expired/self-signed certs, SNI mismatches, OCSP/AIA chains, and TLS 1.0–1.3 server support matrices |
flowchart LR
Client["AI Agent (MCP stdio) / CLI / Python / REST API"] --> Router["TLS Analyzer & Engine Router"]
Router --> Curl["curl_cffi (libcurl-impersonate + BoringSSL)"]
Router --> Boring["boring (wreq Rust + BoringSSL)"]
Router --> Utls["utls (tls-client Go bogdanfinn/uTLS)"]
Router --> OpenSSL["openssl (Python OpenSSL Baseline)"]
Router --> Raw["Raw Socket TLS + X.509 Chain Inspector"]
Curl & Boring & Utls & OpenSSL & Raw --> Target["Target Server / WAF / Cloudflare / Akamai"]Related MCP server: MultiZen MCP Server
Live Proof
FastAPI Swagger UI (/docs)
Interactive OpenAPI 3.1 docs served locally on http://127.0.0.1:8000/docs with all 14 REST endpoints and 8 request/validation schemas:

Real Live JSON Output (boring Chrome vs utls Chrome vs openssl Baseline)
Live responses captured via POST /api/self-fingerprint against https://tls.browserleaks.com/ — boring (Chrome154) and utls (chrome_152) emit authentic Chrome HTTP/2, JA4, Akamai H2, and Windows Chrome User-Agent, whereas standard Python openssl leaks HTTP/1.1 and python-requests/2.34.2:
{
"boring_chrome": {
"success": true,
"engine": "boring",
"profile": "Chrome154",
"endpoint": "https://tls.browserleaks.com/",
"http_version": "HTTP/2",
"fingerprint": {
"ja3_hash": "e1efe648fcaa52bddad1d96b35b9275f",
"ja3n_hash": "bd4930bd9b000ee684830e44bab76fdf",
"ja4": "t13d1517h2_8daaf6152771_cb7bf5808d99",
"ja4_o": "t13d1517h2_acb858a92679_dddf77ad61fc",
"akamai_hash": "52d84b11737d980aef856699f885ca86",
"akamai_text": "1:65536;2:0;4:6291456;6:262144|15663105|0|m,a,s,p",
"user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36"
}
},
"utls_chrome": {
"success": true,
"engine": "utls",
"profile": "chrome_152",
"endpoint": "https://tls.browserleaks.com/",
"http_version": "HTTP/2",
"fingerprint": {
"ja3_hash": "2d25c56381929cc91bc97631a0a46f58",
"ja3n_hash": "bd4930bd9b000ee684830e44bab76fdf",
"ja4": "t13d1517h2_8daaf6152771_cb7bf5808d99",
"ja4_o": "t13d1517h2_acb858a92679_ed4eee291a6e",
"akamai_hash": "52d84b11737d980aef856699f885ca86",
"akamai_text": "1:65536;2:0;4:6291456;6:262144|15663105|0|m,a,s,p",
"user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/152.0.0.0 Safari/537.36"
}
},
"openssl_baseline": {
"success": true,
"engine": "openssl",
"profile": "python-requests-openssl",
"endpoint": "https://tls.browserleaks.com/",
"http_version": "HTTP/1.1",
"fingerprint": {
"ja3_hash": "7291ea5e449f2c7b17582541703e549d",
"ja3n_hash": "e768c332818abbe316c084106db8544a",
"ja4": "t13d1712h1_ab0a1bf427ad_882d495ac381",
"ja4_o": "t13d1712h1_fd0eb050439a_ef7e3bf95d98",
"akamai_hash": "",
"akamai_text": "",
"user_agent": "python-requests/2.34.2"
}
}
}{
"success": true,
"certificate_verified": true,
"host": "tls.browserleaks.com",
"port": 443,
"sni_hostname": "tls.browserleaks.com",
"resolved_ip": "138.197.54.100",
"timings_ms": {
"dns": 11.72,
"tcp_connect": 117.07,
"tls_handshake": 130.31,
"total": 259.1
},
"tls": {
"version": "TLSv1.3",
"cipher_suite": "TLS_AES_128_GCM_SHA256",
"cipher_protocol": "TLSv1.3",
"cipher_bits": 128,
"alpn_protocol": "h2"
},
"certificate": {
"subject": {
"common_name": "tls.browserleaks.com",
"rfc4514": "CN=tls.browserleaks.com"
},
"issuer": {
"common_name": "YE1",
"rfc4514": "CN=YE1,O=Let's Encrypt,C=US"
},
"validity": {
"not_before": "2026-10-05T12:43:04+00:00",
"not_after": "2027-01-03T12:43:03+00:00",
"days_remaining": 52,
"is_expired": false,
"not_yet_valid": false
},
"public_key": {
"type": "EC",
"key_size": 256,
"curve": "secp256r1"
}
}
}4 Independent TLS Engines
Engine | Backend Stack | Profiles | Highlights & Capabilities |
|
| 53 + | Native Chrome / Firefox / Safari / iOS / Edge / Tor profiles, HTTP/1.1, HTTP/2 & HTTP/3, custom |
|
| 139 + | Latest browser enums ( |
|
| 83 + | Wide Go uTLS Chrome/Firefox/Safari/Brave/Opera/OkHttp/mobile identifiers, auto-aligned browser HTTP headers & |
| Python |
| Intentionally un-impersonated baseline control — proves when a |
Friendly aliases likechrome, firefox, safari, safari_ios, edge, opera, okhttp, and random are resolved dynamically against whichever profiles your installed library versions expose — so upgrades never break on hardcoded version numbers.
What You Can Do
1. AI-Native Browserless Access (mcp_server.py)
Exposes 8 MCP tools over stdio with strict Pydantic schemas and descriptions so AI agents (Claude Code, OpenCode, Cursor, Antigravity, etc.) know every parameter automatically:
MCP Tool | What It Does |
| One-call security audit: 0–100 score, A–F grade and severity-sorted findings (expired / soon-to-expire certs, weak RSA/EC/DSA keys, SHA-1/MD5 signatures, self-signed or untrusted chains, legacy TLS 1.0/1.1 still enabled, missing TLS 1.3) |
| Raw socket DNS + TCP + TLS timing breakdown, negotiated TLS version/cipher/ALPN, SANs, full X.509 cert chain (+ unverified fallback on broken/self-signed certs), OCSP/CRL/AIA/extensions & PEMs with |
| Tests |
| Full HTTP/HTTPS client supporting |
| Side-by-side matrix testing multiple browser profiles and/or all 4 engines in bounded parallel ( |
| Verifies the exact |
| Returns all supported engines, aliases, platforms, capabilities, and available profile IDs |
|
|
2. Multi-Step Login & Cookie Persistence (session_id)
Keep the exact pinned TLS configuration (engine, profile, platform, http_version, proxy, verify, ja3) and cookie jar alive across requests without silently drifting mid-session or losing CSRF/session cookies:
from tls_analyzer import probe_tls_fingerprint, manage_tls_session
# Step 1: Hit init/login page cleanly (bypassing TLS WAF check)
init_res = probe_tls_fingerprint(
"https://target.example.com/auth/init",
engine="boring",
profile="chrome",
platform="windows",
session_id="login-flow-1",
full_dump=True,
)
# Step 2: Submit credentials reusing the exact session cookies & client
login_res = probe_tls_fingerprint(
"https://target.example.com/auth/signin",
engine="boring",
method="POST",
json_body={"user": "alice", "password": "secret"},
session_id="login-flow-1",
full_dump=True,
)
# Inspect stored cookies at any time
print(manage_tls_session("inspect", session_id="login-flow-1"))3. Unfiltered Full Dump Mode (full_dump=True)
Default mode keeps output compact (<= 2000 char previews, filtered WAF headers). Turn on full_dump=True (--full-dump in CLI) to remove filters and truncation caps:
All response headers + ordered
raw_headerspairs (preserving duplicateSet-Cookieheaders)Ordered request headers (
request_debug.request_headers_ordered&request_headers_scopeproving customheader_orderalignment)Full cookie objects (
name,value,domain,path,http_only,secure)Complete redirect hop history across all 4 engines (
status_code,url, headers per hop)Unlimited untruncated response body (+
body_base64viainclude_binary_base64=Truefor binary payloads)BoringSSL peer certificate details & PEM (with
engine="boring") and full X.509 extensions / PEMs / shared ciphers (withanalyze_tls)
4. Low-Level TLS, HTTP/2 & Header Overrides
ja3: Custom JA3 string override (curl_cffi&utls)akamai: Custom Akamai HTTP/2 fingerprint string (curl_cffi)header_order: Enforce exact HTTP header wire order acrosscurl_cffi,boring(OrigHeaderMap), andutlsplatform: Spoof OS (windows,macos,linux,android,ios) on bothboringandutlshttp_version: Forcehttp1.1,http2, orhttp3(http3oncurl_cffi)tls_options: Fine-grained native flags (e.g.{"permute_extensions": true, "grease_enabled": true}onboring/curl_cffi, or{"h2_settings": ..., "pseudo_header_order": ..., "connection_flow": ..., "random_tls_extension_order": true}onutls; set{"browser_headers": false}onutlsif you explicitly want raw minimal headers)
5. WAF Detection & Baseline Proof
Every HTTP probe automatically summarizes WAF/CDN signals (cf-ray, cf-mitigated, x-datadome, x-amz-cf-id, x-akamai-transformed, x-sucuri-id, x-px) and, when compare_baseline=True, runs a side-by-side OpenSSL control request so you know immediately if status differences (403 vs 200) are caused by TLS fingerprinting.
Installation & Setup
1. Clone and create a virtual environment
git clone https://github.com/KMG305/tls-analyzer-bypass-mcp.git
cd tls-analyzer-bypass-mcp
python -m venv .venvActivate the virtual environment:
Windows (PowerShell):
.\.venv\Scripts\Activate.ps1macOS / Linux:
source .venv/bin/activate
2. Install dependencies
pip install -r requirements.txt3. Verify tests
python -m unittest discover -s tests -vConfiguring MCP for AI Clients
The MCP server uses stdio transport (mcp_server.py) and always points your AI host directly to the project's .venv Python binary so all TLS backends load cleanly regardless of working directory.
Windows (Claude Desktop / OpenCode / Cursor / Antigravity)
{
"mcpServers": {
"tls-analyzer-bypass-mcp": {
"command": "C:\\path\\to\\tls-analyzer-bypass-mcp\\.venv\\Scripts\\python.exe",
"args": [
"C:\\path\\to\\tls-analyzer-bypass-mcp\\mcp_server.py"
]
}
}
}macOS / Linux
{
"mcpServers": {
"tls-analyzer-bypass-mcp": {
"command": "/absolute/path/to/tls-analyzer-bypass-mcp/.venv/bin/python",
"args": [
"/absolute/path/to/tls-analyzer-bypass-mcp/mcp_server.py"
]
}
}
}Claude Code
claude mcp add tls-analyzer-bypass-mcp -- /absolute/path/to/.venv/bin/python /absolute/path/to/mcp_server.pyCLI Quick Reference
# 1. Raw TLS handshake + full X.509 extensions & PEM certificate chain
python tls_analyzer.py tls.browserleaks.com --full-dump
# 2. Probe TLSv1.0 - TLSv1.3 version support matrix
python tls_analyzer.py cloudflare.com --versions
# 3. Compare all 4 engines side-by-side against one target
python tls_analyzer.py cloudflare.com --engines curl_cffi,boring,utls,openssl --compare-profiles chrome
# 4. POST JSON using BoringSSL (wreq), Windows emulation, custom header order, and full dump
python tls_analyzer.py https://httpbin.org/post --engine boring --fingerprint chrome --platform windows --method POST --header-order "Content-Type,User-Agent" --json '{"hello":"world"}' --full-dump
# 5. Stateful multi-step session with Go uTLS + SOCKS5/HTTP proxy
python tls_analyzer.py https://target.example.com/login --engine utls --fingerprint chrome --session myflow --proxy http://127.0.0.1:8080 --full-dump
# 6. Inspect exact JA3 / JA4 / Akamai H2 & UA emitted on the wire
python tls_analyzer.py --self-fingerprint chrome --engine boring --full-dump
# 7. Security audit (score + grade + findings); exit code 2 if anything >= "high" is found (CI-friendly)
python tls_analyzer.py example.com --audit --fail-on high --expiry-warn-days 21Sample --audit output (abridged):
{
"success": true,
"host": "expired.example.org",
"score": 35,
"grade": "F",
"findings": [
{ "severity": "critical", "code": "CERT_EXPIRED", "title": "Certificate has expired", "recommendation": "Renew and deploy a new certificate immediately." },
{ "severity": "medium", "code": "LEGACY_PROTOCOL_ENABLED", "title": "TLSv1.1 is enabled" }
]
}Scoring: start at 100, subtract 40 / 25 / 10 / 3 per critical / high / medium / low finding; any critical finding forces grade F. Grades: A ≥ 90, B ≥ 80, C ≥ 65, D ≥ 50.
REST API (FastAPI)
Start the API server:
python app.pyRoot Metadata:
http://127.0.0.1:8000/Interactive Swagger Docs:
http://127.0.0.1:8000/docs
Configuration via environment variables:
Variable | Default | Purpose |
|
| Bind address (keep loopback unless you add authentication) |
|
| Listen port |
| (unset) | When set, every |
This API makes outbound connections to arbitrary hosts on behalf of the caller. If you bind it to anything other than loopback, always setTLS_ANALYZER_API_KEY.
Method & Path | Description |
| API metadata and endpoint index |
| Liveness check |
| Full catalog of all 4 engines, aliases, platforms, and profiles |
| Raw TLS handshake + X.509 chain (+ |
| Security audit: score, grade and findings |
|
|
| Single/session HTTP request via any engine (+ |
| Side-by-side multi-profile / multi-engine comparison |
| Live wire JA3 / JA4 / Akamai H2 verification |
| List active persistent cookie/TLS sessions |
| Inspect stored cookies and metadata for a session |
| Clear cookies inside an active session |
| Close a specific session |
| Close all active sessions |
Project Structure
tls-analyzer-bypass-mcp/
├── .github/
│ └── workflows/
│ └── ci.yml # Ruff lint + unittest matrix (Ubuntu/Windows, Python 3.11–3.13)
├── docs/
│ └── swagger-ui.png # Live FastAPI Swagger UI (/docs) screenshot
├── tls_analyzer.py # Core socket engine, X.509 parser, security audit, high-level API & CLI
├── tls_engines.py # Engine drivers (curl_cffi, boring, utls, openssl), presets & SessionRegistry
├── mcp_server.py # Official MCP stdio server exposing 8 AI tools
├── app.py # FastAPI REST API + OpenAPI /docs (optional API-key auth)
├── tests/
│ ├── test_analyzer.py # Unit & local HTTPS integration tests (stdlib unittest)
│ └── test_audit.py # Security audit scoring + REST auth tests
├── pyproject.toml # Ruff configuration
├── .mcp.json # Project-level MCP config
├── claude_desktop_config.example.json # Example Desktop MCP configuration
├── requirements.txt # Python dependencies
├── LICENSE # MIT License
└── .gitignore # Excludes .venv/, __pycache__/, caches, .envLicense
Licensed under the MIT License. See LICENSE for full terms.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Web scraping, browser automation, screenshots and AI data extraction for AI agents via MCP.
Email inboxes, webhook URLs, mock APIs and 170+ tools for coding agents over one MCP connection.
Stealth web browser for agents: search, fetch, click, download and type in persistent MCP sessions.
MCP tools for agents: web research, content extraction, email, DNS, and blockchain intelligence.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides a real browser that bypasses bot detection (Cloudflare, Turnstile) for AI agents, enabling navigation, clicking, typing, screenshots, and data collection through MCP tools.137 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and human operators to drive isolated browser profiles with persistent cookies, fingerprints, and proxies, exposing navigation, clicking, typing, extraction, screenshots, JS evaluation, tabs, cookies, and waits to MCP clients.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to automate anti-detection browser sessions with navigation, interaction, search, extraction, downloads, multi-tab workflows, and session reuse.581 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and human operators to launch and drive isolated, persistent browser profiles — each with its own cookies, fingerprint, and proxy — from any MCP client. Exposes tools for navigating, clicking, typing, extracting content, taking screenshots, evaluating JavaScript, managing tabs and cookies, and waiting on page events.MIT