disasm.dev MCP server
Enables AI assistants to generate DataDome and Incapsula clearance tokens without a headless browser, for development and prototyping.
README
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.
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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.