disasm.dev MCP server
OfficialClick 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., "@disasm.dev MCP server solve a DataDome challenge for https://example.com"
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.
disasm.dev MCP server
A Model Context Protocol server for disasm.dev. It lets an AI assistant (Claude, Cursor, and any MCP client) generate valid DataDome and Incapsula clearance tokens, without a headless browser.
It is built for development and prototyping: solve a challenge inline and have your assistant wire the result into your scraper. Production traffic should call the HTTP API directly.
Tools
Tool | What it does |
| Solve a DataDome |
| Solve an Incapsula (Imperva) |
| Your account profile. |
| Subscription balance and PAYG wallet. |
| Recent solve usage. |
| Your API keys (metadata only). |
Every tool uses one disasm.dev API key. Create one in the dashboard.
Related MCP server: nokk
Install (local, stdio)
Add it to your MCP client. For Claude Desktop, edit claude_desktop_config.json:
{
"mcpServers": {
"disasm": {
"command": "npx",
"args": ["-y", "disasm-mcp"],
"env": { "DISASM_API_KEY": "your_api_key" }
}
}
}The same command / args / env shape works for Cursor and other clients.
Use (remote, HTTP)
The server also runs as a remote Streamable HTTP endpoint. Point your client at the URL and pass your key as a Bearer token:
{
"mcpServers": {
"disasm": {
"url": "https://mcp.disasm.dev/mcp",
"headers": { "Authorization": "Bearer your_api_key" }
}
}
}The hosted endpoint is stateless: each request carries its own key and no key is stored server-side.
Run it yourself
npm install
npm run build
# stdio (what npx runs)
DISASM_API_KEY=your_api_key npm start
# remote HTTP on :8787 (override with PORT)
npm run start:httpConfiguration
Variable | Default | Purpose |
| (required, stdio) | Your disasm.dev API key. |
|
| HTTP server port. |
|
| DataDome solve host. |
|
| Incapsula solve host. |
|
| Management API host. |
Notes
Treat your API key like a password. Anyone with it can spend your balance.
License
MIT. See LICENSE.
Available Tools
6 toolsget_accountGet accountA
Your disasm.dev account profile.
Inputs: no named parameters.
get_balanceGet balanceA
Your subscription request balance and PAYG wallet balance (in pence).
Inputs: no named parameters.
get_usageGet usageB
Your recent solve usage statistics.
Inputs: no named parameters.
list_api_keysList API keysA
List your API keys (metadata only, never the secret value).
Inputs: no named parameters.
solve_datadomeSolve a DataDome challengeA
Generate a valid DataDome clearance payload without a headless browser. Pick challenge='interstitial' (provide device_check_link and device_check_page from the blocked response), 'captcha' (provide captcha_link, the geo.captcha-delivery.com URL), or 'tags'. Returns { success, payload, headers } where headers is the client-hints set to replay on your follow-up request. Each call costs one solve against your balance.
Inputs: challenge (required), params, captcha_link, device_check_link, +1 more.
solve_incapsulaSolve an Incapsula (Imperva) challengeA
Generate an Incapsula clearance token without a headless browser. challenge='reese84' produces a reese84 sensor payload; 'utmvc' solves the ___utmvc cookie. Returns the payload and cookies to replay. Each call costs one solve against your balance.
Inputs: challenge (required), site, params.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool has a distinct and clear purpose: account info, balance, usage, API key listing, and two different captcha-solving tools (DataDome and Incapsula). No overlap in functionality.
Most tools follow a verb_noun pattern with snake_case (e.g., get_account, solve_datadome). The only minor inconsistency is using both 'get_' and 'list_' for retrieval operations, but they are still clearly distinguished.
With 6 tools, the server is well-scoped for its purpose—managing an account and solving captchas. Each tool earns its place without redundancy or excessive complexity.
The tool set covers core account operations (profile, balance, usage, API keys) and two major captcha-solving challenges. Missing features like creating/deleting API keys or additional captcha types are minor gaps for the stated domain.
Maintenance
Related MCP Connectors
Cloudflare Solver: Scraping API designed to bypass Cloudflare protection.
Undetectable cloud browser sessions for AI agents and scrapers. Navigate, extract, click, captcha.
Solve reCAPTCHA image grids, text captchas, GeeTest and FunCAPTCHA for AI agents. Free tier.
Solve reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstile and image captchas. Platform-hosted, no creden
Related MCP Servers
AlicenseAqualityDmaintenanceEnables AI agents to scrape websites protected by Cloudflare, DataDome, and Akamai, bypassing anti-bot measures to retrieve page content.2MIT- AlicenseAqualityBmaintenanceHeadless browser for AI agents with Chrome's fingerprint that passes Cloudflare challenges.121228Apache 2.0

guru.cap/capguru-mcpofficial
AlicenseBqualityBmaintenanceIt enables AI assistants and agents to open web pages, detect and solve captchas such as reCAPTCHA, hCaptcha, Turnstile, FunCaptcha, GeeTest, and SmartCaptcha, and continue tasks by interacting with browser elements. It also supports obtaining tokens without a browser for some captcha types and recognizing text captchas.171MIT- AlicenseAqualityBmaintenanceEnables MCP clients like Claude and Cursor to solve CAPTCHA and anti-bot challenges — Turnstile, DataDome, Akamai, PerimeterX, Imperva, AWS WAF, FunCaptcha and image OCR — through a single API. Returns tokens, clearance cookies or recognized text, with task creation, polling, cancellation, balance and price lookups.8MIT