Skip to main content
Glama
disasm.dev MCP server

disasm.dev MCP server

Official
by disasm-dev

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_datadome

Solve a DataDome interstitial, captcha, or tags challenge. Returns the payload and client-hint headers to replay.

solve_incapsula

Solve an Incapsula (Imperva) reese84 or utmvc challenge.

get_account

Your account profile.

get_balance

Subscription balance and PAYG wallet.

get_usage

Recent solve usage.

list_api_keys

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:http

Configuration

Variable

Default

Purpose

DISASM_API_KEY

(required, stdio)

Your disasm.dev API key.

PORT

8787

HTTP server port.

DISASM_DATADOME_URL

https://dd.antibotapi.com

DataDome solve host.

DISASM_INCAPSULA_URL

https://incap.antibotapi.com

Incapsula solve host.

DISASM_API_URL

https://api.disasm.dev

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 tools
get_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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to scrape websites protected by Cloudflare, DataDome, and Akamai, bypassing anti-bot measures to retrieve page content.
      2
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      It 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.
      17
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      8
      MIT