Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

blueDEX

REMOTE · DEX.MK · SCANNED SEP 25

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

Available components

68 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security69
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 65% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

remote · dex.mk

# add to Claude Code
claude mcp add --transport http mk-dex-bluedex 'https://dex.mk/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "mk-dex-bluedex": {
      "url": "https://dex.mk/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mk-dex-bluedex": {
      "type": "http",
      "url": "https://dex.mk/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add mk-dex-bluedex --url 'https://dex.mk/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  mk-dex-bluedex:
    url: "https://dex.mk/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mk-dex-bluedex": {
      "Transport": "http",
      "Url": "https://dex.mk/mcp"
    }
  }
}
# add to Vellum
assistant mcp add mk-dex-bluedex -t streamable-http -u 'https://dex.mk/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Probed https://dex.mk/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dex.mk CN=WE1,O=Google Trust Services,C=US 15 Aug 2026 13 Nov 2026 ECDSA 256 ECDSA-SHA256 c84a6069f06d30d8132a4d9be8440e5c
SANs: dex.mk, www.dex.mk, *.www.dex.mk
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dex.mk. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
mk. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self'; connect-src 'self' https: wss:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy geolocation=(), microphone=(), camera=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dex.mk/mcp Verified 200
http (plaintext) http://dex.mk/mcp Inconclusive 405
MCP tools · 10 exposed · ~1,244 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
build_swap_transaction ~148

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.

NameTypeReqDescription
amountstringyes–
buyobjectyes–
sellobjectyes–
slippageBpsnumber––
sourcestringyesVenue id from the quote (e.g. 'lifi', 'jupiter')
takerstringyesThe address that will sign and execute

No output schema declared.

No examples provided.

create_instant_shift ~168

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.

NameTypeReqDescription
fromstringyesinstant asset id to send, e.g. 'usdc-base'
refundAddressstring–optional: refund destination if the shift fails or expires
settleAddressstringyesyour receiving address for the `to` asset
tostringyesinstant asset id to receive, e.g. 'usdt-tron'

No output schema declared.

No examples provided.

get_chart ~73

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

NameTypeReqDescription
addressstringyes–
chainstringyes–
timeframestring–default 1h

No output schema declared.

No examples provided.

get_instant_status ~56

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.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_meta ~40

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_swap_quote ~138

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.

NameTypeReqDescription
amountstringyesInteger amount in base units of the sell token, e.g. '100000000000000000' for 0.1 WETH
buyobjectyes–
sellobjectyes–
slippageBpsnumber–Max slippage in basis points, default 50

No output schema declared.

No examples provided.

list_instant_assets ~62

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_onramps ~156

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_route ~219

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.

NameTypeReqDescription
amountstringyesinteger base units of `from`
from–yesinstant id string (e.g. 'usdt-tron') OR a DEX token {chain,address}
to–yesinstant id string OR a DEX token {chain,address}

No output schema declared.

No examples provided.

sweep_dust ~184

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.

NameTypeReqDescription
chainstring–default base
dustarrayyestokens to sweep: [{ address, amount (integer base units), symbol?, decimals? }]
slippageBpsnumber–default 100
targetTokenstring–consolidate into this token (default USDC)
walletstringyesyour 0x address (the taker)

No output schema declared.

No examples provided.

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.