disasm.dev MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | HTTP server port | 8787 |
| DISASM_API_KEY | Yes | Your disasm.dev API key | |
| DISASM_API_URL | No | Management API host | https://api.disasm.dev |
| DISASM_DATADOME_URL | No | DataDome solve host | https://dd.antibotapi.com |
| DISASM_INCAPSULA_URL | No | Incapsula solve host | https://incap.antibotapi.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| solve_datadomeA | 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. |
| solve_incapsulaA | 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. |
| get_accountA | Your disasm.dev account profile. |
| get_balanceA | Your subscription request balance and PAYG wallet balance (in pence). |
| get_usageB | Your recent solve usage statistics. |
| list_api_keysA | List your API keys (metadata only, never the secret value). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.