No private key appears anywhere in the surface: both creation tools take addresses and return a transaction, which puts the irreversible step outside this server entirely. The three read tools exist because the two write tools need exact values — a chain that is genuinely supported, and a token resolved to its address on that chain. get_instructions telling you to call it first is unusual advice and worth taking, because create_tx's argument list is long and order-authority addresses are precisely the kind of value that gets guessed wrongly.
A five-tool deBridge server covering the instruction guide, token and chain lookup, and cross-chain or same-chain swap transaction creation.
- get_instructions, returning the full guide for this server — its own description says to call it first
- search_tokens across the deBridge token database by name, symbol or contract address, scoped to a chain
- get_supported_chains, the networks deBridge covers for cross-chain swaps
- create_tx, building a cross-chain swap through the DLN protocol from source and destination chains, tokens and amounts, the order authority address on each chain, the recipient, an affiliate fee and an operating-expense flag
- transaction_same_chain_swap, building a same-chain swap with slippage, a source-chain priority level and an affiliate fee
Nothing configured through this server. Both creation tools take the addresses as arguments — the sender, the order authority on each chain and the recipient — and neither signs anything.
One command — npx -y @debridge-finance/debridge-mcp@latest