Remote MCP · Endpoint

blueDEX MCP server

No. blueDEX answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://dex.mk/mcp

The last check completed an MCP handshake.

Registry name
mk.dex/bluedex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
536 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Non-custodial DEX aggregator for autonomous AI agents: best-price swaps on 8 chains, no API key.
Listing
From the official MCP registry (active).
Recent checks of blueDEX
CheckedResultHandshake
2 hours agoHandshake completed536 ms
2 days agoHandshake completed1.60 s
4 days agoHandshake completed367 ms
5 days agoHandshake completed198 ms
7 days agoHandshake completed303 ms
8 days agoHandshake completed534 ms
9 days agoHandshake completed454 ms
12 days agoHandshake completed423 ms
13 days agoHandshake completed476 ms
15 days agoHandshake completed460 ms
17 days agoHandshake completed521 ms
18 days agoHandshake completed230 ms
19 days agoHandshake completed507 ms
20 days agoHandshake completed485 ms
20 days agoHandshake completed215 ms
21 days agoHandshake completed455 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with blueDEX and makes no claim about it beyond what these checks measured.