bridging_bridgeDeBridge
InactiveTool of SAP MCP Server
Bridge tokens across chains via deBridge DLN. Fast cross-chain transfers with deterministic pricing. SAP MCP context: Protocol bridging; operation class write. Use for cross-chain asset movement through Wormhole or deBridge. Confirm source chain, destination chain, token mint, amount, recipient, route fees, and finality expectations before invoking a bridge write. For bridge flows call the matching status tool after submission. If the bridge capability belongs to a registered SAP agent, plan the profile with sap_agent_identity_plan, register through sap_payments_register_agent, then advertise bridge capability IDs with sap_payments_update_agent or sap_publish_tool_by_name.
Parameters schema
{
"type": "object",
"required": [
"sourceChain",
"destinationChain",
"tokenIn",
"tokenOut",
"amount",
"sender",
"recipient"
],
"properties": {
"amount": {
"type": "string",
"description": "Amount to bridge (raw)"
},
"sender": {
"type": "string",
"description": "Sender address"
},
"tokenIn": {
"type": "string",
"description": "Token address on source chain"
},
"tokenOut": {
"type": "string",
"description": "Token address on destination chain (use \"0x0\" for native)"
},
"recipient": {
"type": "string",
"description": "Recipient address on destination chain"
},
"slippageBps": {
"type": "number",
"description": "Slippage tolerance in bps"
},
"sourceChain": {
"type": "number",
"description": "Source chain ID (e.g. 7565164 for Solana)"
},
"destinationChain": {
"type": "number",
"description": "Destination chain ID"
}
},
"additionalProperties": false
}No endpoints wrapped at confidence ≥ 0.70.
Parent server
SAP MCP Server
https://github.com/OOBE-PROTOCOL/sap-mcp
2/7 registries