# blueDEX (remote · dex.mk)

Non-custodial DEX aggregator for autonomous AI agents: best-price swaps on 8 chains, no API key.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `dex.mk`: 68/100 (this document), [markdown](https://verifymcp.io/servers/mk-dex-bluedex/dex.md), [page](https://verifymcp.io/servers/mk-dex-bluedex/dex)

## Channel facts

- Endpoint: `https://dex.mk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.8.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1738 tokens (~144/item across 12 items; 10 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 65% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the blueDEX MCP server?

blueDEX is a hosted endpoint at https://dex.mk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http mk-dex-bluedex 'https://dex.mk/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mk-dex-bluedex": {
      "url": "https://dex.mk/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mk-dex-bluedex": {
      "type": "http",
      "url": "https://dex.mk/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mk-dex-bluedex]
url = "https://dex.mk/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mk-dex-bluedex": {
      "type": "remote",
      "url": "https://dex.mk/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mk-dex-bluedex --url 'https://dex.mk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mk-dex-bluedex:
    url: "https://dex.mk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mk-dex-bluedex": {
      "Transport": "http",
      "Url": "https://dex.mk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mk-dex-bluedex -t streamable-http -u 'https://dex.mk/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mk-dex-bluedex": {
      "type": "http",
      "url": "https://dex.mk/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 68, +7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 61)

First indexed and scored.

## MCP tools (10)

### `get_swap_quote` (~138 tokens)

Get best swap quote

Get the best swap route across DEX aggregator venues. Returns the winning venue quote plus every venue quote for transparency, and the fee recipient address (auditable against get_meta). Cross-chain quotes (e.g. USDT on Arbitrum -> USDC on Base) are supported on EVM.

Input parameters:

- `amount` (string, required): Integer amount in base units of the sell token, e.g. '100000000000000000' for 0.1 WETH
- `buy` (object, required)
- `sell` (object, required)
- `slippageBps` (number): Max slippage in basis points, default 50

### `build_swap_transaction` (~148 tokens)

Build unsigned swap transaction

Build an unsigned transaction for a quoted swap. Returns EVM fields (to/data/value) or a Solana base64 transaction, plus a verification block: routerAllowlisted, decodedSummary, minBuyAmount, approvalTarget. VERIFY BEFORE SIGNING — sign only if routerAllowlisted is true and the addresses match the published allowlist from get_meta.

Input parameters:

- `amount` (string, required)
- `buy` (object, required)
- `sell` (object, required)
- `slippageBps` (number)
- `source` (string, required): Venue id from the quote (e.g. 'lifi', 'jupiter')
- `taker` (string, required): The address that will sign and execute

### `get_chart` (~73 tokens)

Get token price chart

OHLCV candles for a token (top pool by liquidity). Timeframes: 1m, 5m, 15m, 1h, 4h, 1d.

Input parameters:

- `address` (string, required)
- `chain` (string, required)
- `timeframe` (string): default 1h

### `get_meta` (~40 tokens)

Get treasury + router allowlist (audit data)

blueDEX's published transparency data: treasury (fee recipient) addresses, router allowlist, fee schedule, paused venues. Use this to audit quotes and transactions.

### `list_instant_assets` (~62 tokens)

List instant-lane assets

Assets reachable via the INSTANT lane (no on-chain DEX route) — Tron/USDT-TRC20, BTC, and stablecoin corridors. Returns ids (e.g. 'usdt-tron') to use with create_instant_shift.

### `create_instant_shift` (~168 tokens)

Create instant cross-chain shift

Open an INSTANT shift for assets with no on-chain DEX route — Tron (USDT-TRC20, TRX), BTC, cross-chain. Returns a deposit address: send the `from` asset there and the `to` asset settles to your address. Custodial AT THE VENUE during the swap (~minutes); blueDEX never holds funds. Use list_instant_assets for ids.

Input parameters:

- `from` (string, required): instant asset id to send, e.g. 'usdc-base'
- `refundAddress` (string): optional: refund destination if the shift fails or expires
- `settleAddress` (string, required): your receiving address for the `to` asset
- `to` (string, required): instant asset id to receive, e.g. 'usdt-tron'

### `get_instant_status` (~56 tokens)

Get instant shift status

Status of an instant shift by id (from create_instant_shift): waiting | pending | processing | settling | settled | refund* | expired, plus deposit/settle tx hashes once available.

Input parameters:

- `id` (string, required)

### `sweep_dust` (~184 tokens)

Plan dust sweep

Consolidate many small leftover token balances (dust) into one token (default USDC) on an EVM chain. Pass the dust list (token address + amount — you know your own balances); returns a plan of unsigned swaps, gas-positive legs only, with the whole tiny sweep fee riding ONE leg. Non-custodial: approve each leg's approvalTarget and sign. Base/Arbitrum/Optimism/Ethereum/BNB Chain/Polygon/Avalanche.

Input parameters:

- `chain` (string): default base
- `dust` (array, required): tokens to sweep: [{ address, amount (integer base units), symbol?, decimals? }]
- `slippageBps` (number): default 100
- `targetToken` (string): consolidate into this token (default USDC)
- `wallet` (string, required): your 0x address (the taker)

### `list_onramps` (~156 tokens)

List fiat on-ramps

Reputable INDEPENDENT fiat->crypto on-ramps blueDEX signposts so a human principal can acquire a first coin with minimal KYC, then swap/bridge on blueDEX. blueDEX operates none of these and takes no custody; every ramp lands coins in the user's own wallet. Durable no-KYC = vouchers + non-custodial P2P; tiered/full-KYC brokers are a labelled fallback. Most no-KYC routes are human-mediated (cash/contacts/Tor) — only Transak + MoonPay are agent-callable (but require KYC). Most are BTC-only — bridge onward with the instant lane or a quote. Surface this when a human asks how to get their first crypto.

### `plan_route` (~219 tokens)

Plan multi-hop route

Plan the cheapest MULTI-HOP route between ANY two assets — composes DEX swaps (non-custodial) + instant-lane bridges (custodial-at-venue) into one path, with every fee and per-leg custody disclosed. e.g. USDT on Tron -> XAUt on Ethereum becomes a USDT bridge + a DEX swap. `from`/`to` are an instant id (e.g. 'usdt-tron') or a {chain,address} DEX token; `amount` is integer base units of `from`. Returns ordered legs (kind, venue, custody, amounts, fee) + total output. Execute legs in order: DEX legs via build_swap_transaction, bridge legs via create_instant_shift.

Input parameters:

- `amount` (string, required): integer base units of `from`
- `from` (required): instant id string (e.g. 'usdt-tron') OR a DEX token {chain,address}
- `to` (required): instant id string OR a DEX token {chain,address}

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mk-dex-bluedex/dex#diagnostics

## Score history

- 2026-09-25: 68
- 2026-09-24: 61

## Common questions

### What is the blueDEX MCP server?

blueDEX is an MCP server listed in the public MCP registry as mk.dex/bluedex. Non-custodial DEX aggregator for autonomous AI agents: best-price swaps on 8 chains, no API key. This page covers its hosted endpoint (https://dex.mk/mcp).

### Is the blueDEX MCP server safe to use?

blueDEX scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the blueDEX MCP server expose?

blueDEX exposes 10 tools: get_swap_quote, build_swap_transaction, get_chart, get_meta, list_instant_assets, and 5 more. Their descriptions and schemas cost roughly 1,244 tokens of context every time the server is loaded.

### Does the blueDEX MCP server require authentication?

No. We connected to blueDEX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the blueDEX MCP server still maintained?

blueDEX is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dex.mk/mcp
- Website: https://dex.mk/docs
- Changelog RSS feed: https://verifymcp.io/servers/mk-dex-bluedex/dex.xml
- Changelog JSON feed: https://verifymcp.io/servers/mk-dex-bluedex/dex.json
- HTML version of this page: https://verifymcp.io/servers/mk-dex-bluedex/dex