bridging_bridgeWormhole
InactiveTool of SAP MCP Server
Bridge tokens across chains via Wormhole. Supports Solana ↔ EVM chains. 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",
"token",
"amount",
"sender",
"recipient"
],
"properties": {
"token": {
"type": "string",
"description": "Token address on source chain"
},
"amount": {
"type": "string",
"description": "Amount to bridge (raw, smallest unit)"
},
"sender": {
"type": "string",
"description": "Sender wallet on source chain"
},
"recipient": {
"type": "string",
"description": "Recipient address on destination chain"
},
"relayerFee": {
"type": "string",
"description": "Raw token amount (smallest unit, no decimals)"
},
"sourceChain": {
"type": "string",
"description": "Source chain identifier (e.g. \"solana\", \"ethereum\", \"base\", \"polygon\")"
},
"destinationChain": {
"type": "string",
"description": "Destination chain identifier"
}
},
"additionalProperties": false
}No endpoints wrapped at confidence ≥ 0.70.
Parent server
SAP MCP Server
https://github.com/OOBE-PROTOCOL/sap-mcp
2/7 registries