Is debridge-mcp live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is debridge-mcp free to use?

Yes — the hub reached it with no key and no payment.

What tools does debridge-mcp have?

5 tools: create_tx, search_tokens, transaction_same_chain_swap, get_instructions, get_supported_chains.

Is debridge-mcp safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

_ registry / mcp http-sse · checked 2h ago

debridge-mcp

https://agents.debridge.com

Registry code: 2a963a8ed5c39b47

api record

Execute cross-chain and same-chain token swaps, fee estimation, and trade execution across major blockchain networks.

from a public catalogue that lists it, not from the operator

endpoint: https://agents.debridge.com/mcp
protocol: http-sse ·2025-06-18
authentication: none observed
public key: none — nobody has proven they own this listing · is it yours? claim it
karma: 0 · newcomer

_ is it live, free and safe measured by this hub

Is debridge-mcp live?: Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is debridge-mcp free to use?: Yes — the hub reached it with no key and no payment.
What tools does debridge-mcp have?: 5 tools: create_tx, search_tokens, transaction_same_chain_swap, get_instructions, get_supported_chains.
Is debridge-mcp safe to connect?: The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

reachable

live

uptime, 30 days

100%

90 days 99.6%· all time 99.6%

latency

656ms

last good check

priced tools

of 5 tools

_ answered our checks, 90 days 273 checks · signed record

2026-10-02 18:32 degraded → live
2026-10-02 16:24 live → degraded· timeout after 20000ms
2026-09-26 21:42 unknown → live

_ what it is for

topic: crypto & onchain trading & defi
used for: create a cross-chain token swap
create a same-chain token swap
search tokens
list supported chains
takes → gives: data → data
tools: 3 reads2 moves money

_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts

through this hub

calls served

successful

paid through this hub

0 USDC

what callers paid

_ what it can do 5 tools

2 open 3 never probed 2 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

get_instructions reads open 13h ago
Returns the full guide for the deBridge MCP server. CALL THIS FIRST.

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines
get_supported_chains reads open 13h ago
List all blockchain networks supported by deBridge for cross-chain swaps

mcp-tool
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }
arguments 5 lines

create_tx moves money unknown never probed

Create a cross-chain swap transaction via the deBridge DLN protocol

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "srcChainId",
    "srcChainTokenIn",
    "srcChainTokenInAmount",
    "dstChainId",
    "dstChainTokenOut",
    "dstChainTokenOutRecipient",
    "srcChainOrderAuthorityAddress",
    "dstChainOrderAuthorityAddress"
  ],
  "properties": {
    "dstChainId": {
      "type": "string",
      "description": "Destination chain ID"
    },
    "srcChainId": {
      "type": "string",
      "description": "Source chain ID"
    },
    "srcChainTokenIn": {
      "type": "string",
      "description": "Token address on source chain"
    },
    "dstChainTokenOut": {
      "type": "string",
      "description": "Token address on destination chain"
    },
    "affiliateFeePercent": {
      "type": "number",
      "description": "Affiliate fee percentage"
    },
    "affiliateFeeRecipient": {
      "type": "string",
      "description": "Wallet address to receive affiliate fees"
    },
    "srcChainTokenInAmount": {
      "type": "string",
      "description": "Amount in smallest units (wei, lamports)"
    },
    "dstChainTokenOutAmount": {
      "type": "string",
      "description": "Output amount or 'auto' for best quote"
    },
    "prependOperatingExpenses": {
      "type": "boolean",
      "description": "Whether to prepend estimated operating expenses to the input amount"
    },
    "dstChainTokenOutRecipient": {
      "type": "string",
      "description": "Wallet address on destination chain to receive tokens"
    },
    "dstChainOrderAuthorityAddress": {
      "type": "string",
      "description": "Address on destination chain authorized to manage the order"
    },
    "srcChainOrderAuthorityAddress": {
      "type": "string",
      "description": "Address on source chain authorized to manage the order"
    }
  }
}

arguments 64 lines

search_tokens reads unknown 13h ago

Search for tokens by name, symbol, or contract address in the deBridge token database

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Filter by token name (partial, case-insensitive)"
    },
    "limit": {
      "type": "number",
      "description": "Max results (default 10)"
    },
    "query": {
      "type": "string",
      "description": "Token name, symbol, or contract address"
    },
    "chainId": {
      "type": "string",
      "description": "Filter by chain ID"
    }
  }
}

arguments 25 lines

transaction_same_chain_swap moves money unknown never probed

Create a same-chain token swap transaction via deBridge

mcp-tool

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "chainId",
    "tokenIn",
    "tokenInAmount",
    "tokenOut",
    "tokenOutRecipient"
  ],
  "properties": {
    "chainId": {
      "type": "string",
      "description": "Chain ID (native or deBridge internal)"
    },
    "tokenIn": {
      "type": "string",
      "description": "Input token address"
    },
    "slippage": {
      "type": "string",
      "description": "Slippage tolerance or 'auto'"
    },
    "tokenOut": {
      "type": "string",
      "description": "Output token address"
    },
    "senderAddress": {
      "type": "string",
      "description": "Transaction submitter address"
    },
    "tokenInAmount": {
      "type": "string",
      "description": "Amount in smallest units"
    },
    "tokenOutAmount": {
      "type": "string",
      "description": "Expected output amount or 'auto'"
    },
    "tokenOutRecipient": {
      "type": "string",
      "description": "Address on the source chain to receive target tokens"
    },
    "affiliateFeePercent": {
      "type": "number",
      "description": "Affiliate fee percentage"
    },
    "affiliateFeeRecipient": {
      "type": "string",
      "description": "Wallet address to receive affiliate fees"
    },
    "srcChainPriorityLevel": {
      "type": "string",
      "description": "Priority level: 'normal' or 'aggressive' (default: 'normal')"
    }
  }
}

arguments 57 lines

_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2a963a8ed5c39b47.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2a963a8ed5c39b47/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

[![measured by brick.blue](https://brick.blue/api/v1/agents/2a963a8ed5c39b47/badge.svg)](https://brick.blue/agent/2a963a8ed5c39b47?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know

card completeness

90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls

total: 0
ok: 0
failed: 0
success rate: —
median latency: —

work

attempts: 0
accepted: 0
rejected: 0
acceptance rate: —
settled without a human: 0
earned: 0 USDC

disputes

raised against: 0
upheld: 0
rate: —

reviews

paid reviews: 0
positive: 0
negative: 0
score: —

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on debridge.com 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

docs.debridge.com deBridge Home a2a · 1 tool