mcp-registry/mk.dex/bluedex · v0.8.0
As of 2026-10-27 07:02 UTC, the Dex Bluedex MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Non-custodial DEX aggregator for autonomous AI agents: best-price swaps on 8 chains, no API key.
Point your MCP client at this streamable-http endpoint: https://dex.mk/mcp
9 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fmk.dex%2Fbluedex/fixes
{
"name": "plan_route",
"description": "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 leg",
"inputSchema": {
"type": "object",
"required": [
"from",
"to",
"amount"
],
"properties": {
"to": {
"description": "instant id string OR a DEX token {chain,address}",
"type": "string"
},
"from": {
"description": "instant id string (e.g. 'usdt-tron') OR a DEX token {chain,address}",
"type": "string"
},
"amount": {
"type": "string",
"description": "integer base units of `from`"
}
}
},
"annotations": {
"title": "Plan multi-hop route",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
},
"title": "Plan multi-hop route"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/mk.dex/bluedex"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/mk.dex/bluedex"}) over MCP.
build_swap_transaction ~379 tokensget_swap_quote ~350 tokenssweep_dust ~325 tokensplan_route ~238 tokenscreate_instant_shift ~228 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fmk.dex%2Fbluedex?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fmk.dex%2Fbluedex?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fmk.dex%2Fbluedex.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fmk.dex%2Fbluedex.svg :target: https://glimind.com/server/mcp-registry%2Fmk.dex%2Fbluedex?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3e78b9b8ae2a1e1d…, first seen 2026-10-17, included at leaf 9988 of 77,973. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 07:02 UTC, the Dex Bluedex MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Dex Bluedex MCP server advertises 10 tools, including build_swap_transaction, create_instant_shift, get_chart, get_instant_status, get_meta.
Point your MCP client at this streamable-http endpoint: https://dex.mk/mcp
Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.