ai.oobeprotocol.sap.mcp/sap-mcp

Est-ce que ai.oobeprotocol.sap.mcp/sap-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « ai.oobeprotocol.sap.mcp/sap-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 453 outils

• 3land_buyNFT≈ 646 tokens

  Purchase an NFT from a 3.Land listing. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • buyer · string · requis
    Solana public key (base58)
  • listingId · string · requis
    3.Land listing ID

  Exemple d'appel

  {"name": "3land_buyNFT", "arguments": {"buyer": "texte", "listingId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• 3land_cancelListing≈ 645 tokens

  Cancel an active NFT listing on 3.Land. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • seller · string · requis
    Solana public key (base58)
  • listingId · string · requis
    3.Land listing ID to cancel

  Exemple d'appel

  {"name": "3land_cancelListing", "arguments": {"seller": "texte", "listingId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• 3land_createCollection≈ 839 tokens

  Create a new NFT collection on 3.Land marketplace. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (7)

  Paramètres

  • name · string · requis
    Collection name
  • image · string · requis
    Collection cover image URL
  • owner · string · requis
    Collection owner wallet
  • symbol · string · requis
    Collection symbol
  • creators · array · optionnel
    Creators parameter for 3land Create Collection.
  • royaltyBps · number · optionnel
    Royalty Bps parameter for 3land Create Collection.
  • description · string · optionnel
    Collection description

  Exemple d'appel

  {"name": "3land_createCollection", "arguments": {"name": "texte", "image": "texte", "owner": "texte", "symbol": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• 3land_listForSale≈ 704 tokens

  List an NFT for sale on 3.Land in any SPL token. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (5)

  Paramètres

  • mint · string · requis
    NFT mint to list
  • price · string · requis
    Listing price (in specified token)
  • expiry · string · optionnel
    ISO 8601 listing expiry timestamp
  • seller · string · requis
    Solana public key (base58)
  • priceMint · string · optionnel
    NFT mint address (base58)

  Exemple d'appel

  {"name": "3land_listForSale", "arguments": {"mint": "texte", "price": "texte", "seller": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• 3land_mintAndList≈ 929 tokens

  Mint an NFT on 3.Land and automatically list it for sale. SAP MCP context: Protocol 3land; operation class write. Use for 3.Land NFT collection, minting, listing, cancellation, and purchase flows. Confirm marketplace price, seller/buyer wallet, collection, and listing state before writes. Pair marketplace actions with SAP registry metadata only when the marketplace asset is part of the agent identity or service catalog. SAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (9)

  Paramètres

  • name · string · requis
    Name name or domain value used by 3land Mint And List.
  • image · string · requis
    NFT image URL
  • owner · string · requis
    Solana public key (base58)
  • price · string · requis
    Listing price in token amount
  • supply · number · optionnel
    Edition supply
  • priceMint · string · optionnel
    NFT mint address (base58)
  • attributes · array · optionnel
    Attributes parameter for 3land Mint And List.
  • collection · string · requis
    3.Land collection ID
  • description · string · optionnel
    Description parameter for 3land Mint And List.

  Exemple d'appel

  {"name": "3land_mintAndList", "arguments": {"name": "texte", "image": "texte", "owner": "texte", "price": "texte", "collection": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• adrena_addCollateral≈ 653 tokens

  Add collateral to an existing Adrena position. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • amount · string · requis
    Raw token amount (smallest unit)
  • wallet · string · requis
    Solana public key (base58)
  • positionKey · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "adrena_addCollateral", "arguments": {"amount": "texte", "wallet": "texte", "positionKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• adrena_closePosition≈ 630 tokens

  Close a perpetual position on Adrena Protocol. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)
  • positionKey · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "adrena_closePosition", "arguments": {"wallet": "texte", "positionKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• adrena_getPositions≈ 585 tokens

  Get all open positions on Adrena Protocol. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "adrena_getPositions", "arguments": {"wallet": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• adrena_openPosition≈ 775 tokens

  Open a leveraged perpetual position on Adrena Protocol. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (8)

  Paramètres

  • side · string · requis · long | short
    Side parameter for Adrena Open Position.
  • market · string · requis
    Market symbol (e.g. "SOL", "BTC", "ETH")
  • wallet · string · requis
    Solana public key (base58)
  • leverage · number · requis
    Leverage multiplier
  • stopLoss · number · optionnel
    Stop loss price
  • takeProfit · number · optionnel
    Take profit price
  • collateralMint · string · requis
    Collateral token mint (e.g. USDC, SOL)
  • collateralAmount · string · requis
    Raw token amount (smallest unit)

  Exemple d'appel

  {"name": "adrena_openPosition", "arguments": {"side": "long", "market": "texte", "wallet": "texte", "leverage": 1, "collateralMint": "texte", "collateralAmount": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• adrena_removeCollateral≈ 655 tokens

  Remove collateral from an Adrena position. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • amount · string · requis
    Raw token amount (smallest unit)
  • wallet · string · requis
    Solana public key (base58)
  • positionKey · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "adrena_removeCollateral", "arguments": {"amount": "texte", "wallet": "texte", "positionKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• alldomains_getOwnedDomains≈ 577 tokens

  Get all domains owned by a wallet across all TLDs. SAP MCP context: Protocol alldomains; operation class read. Use to list domains owned by a wallet through AllDomains. Use as discovery context before choosing a name to associate with an agent. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • tld · string · optionnel
    Filter by TLD
  • wallet · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "alldomains_getOwnedDomains", "arguments": {"wallet": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• alldomains_registerDomain≈ 656 tokens

  Register a domain on AllDomains (supports multiple TLDs: .abc, .bonk, .poor, etc.). SAP MCP context: Protocol alldomains; operation class write. Use for AllDomains name registration and resolution workflows. Confirm domain, TLD, owner, and renewal or purchase terms before writes. Use only when the requested name service is not SNS-specific. SAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • tld · string · optionnel
    TLD if not included in domain string
  • domain · string · requis
    Full domain (e.g. "myname.abc", "trader.bonk")
  • wallet · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "alldomains_registerDomain", "arguments": {"domain": "texte", "wallet": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• alldomains_resolveDomain≈ 557 tokens

  Resolve a multi-TLD domain to its owner wallet. SAP MCP context: Protocol alldomains; operation class read. Use to resolve an AllDomains name without changing ownership or records. Use only when the requested name service is not SNS-specific. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    Full domain to resolve

  Exemple d'appel

  {"name": "alldomains_resolveDomain", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• blinks_buildActionUrl≈ 642 tokens

  Build and optionally wrap a Solana Action URL for sharing as a Blink. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • params · object · optionnel
    Template parameters to encode
  • baseUrl · string · requis
    Action API endpoint
  • blinkProvider · string · optionnel · dial.to | phantom | backpack | none
    Optionally wrap in a Blink provider URL

  Exemple d'appel

  {"name": "blinks_buildActionUrl", "arguments": {"baseUrl": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• blinks_confirmAction≈ 642 tokens

  Confirm a completed Solana Action by sending the tx signature back to the Action provider. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • actionUrl · string · requis
    Action URL parameter for Blinks Confirm Action.
  • signature · string · requis
    Transaction signature after signing and submitting

  Exemple d'appel

  {"name": "blinks_confirmAction", "arguments": {"actionUrl": "texte", "signature": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• blinks_executeAction≈ 691 tokens

  Execute a Solana Action — sends wallet to the Action endpoint and receives a transaction to sign. SAP MCP context: Protocol blinks; operation class write. Use to execute a Solana Action POST flow. Confirm the action metadata, parameters, expected transaction, and user intent before invoking. Preview and validate action output before signing or submitting any returned transaction through SAP transaction tools. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • params · object · optionnel
    Key-value parameters to fill Action template variables
  • wallet · string · requis
    User wallet to sign the transaction
  • actionUrl · string · requis
    Action endpoint URL (from getAction links)

  Exemple d'appel

  {"name": "blinks_executeAction", "arguments": {"wallet": "texte", "actionUrl": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• blinks_getAction≈ 598 tokens

  Fetch metadata for a Solana Action (Blink) — returns title, description, available actions, and parameters. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • actionUrl · string · requis
    Solana Action URL (https endpoint implementing the Actions spec)

  Exemple d'appel

  {"name": "blinks_getAction", "arguments": {"actionUrl": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• blinks_resolveBlinkUrl≈ 594 tokens

  Resolve a Blink URL (e.g. dial.to link) to its underlying Solana Action URL. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • blinkUrl · string · requis
    Blink URL (e.g. https://dial.to/?action=solana-action:...)

  Exemple d'appel

  {"name": "blinks_resolveBlinkUrl", "arguments": {"blinkUrl": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• blinks_validateActionsJson≈ 606 tokens

  Validate a domain's actions.json file — checks if a website correctly implements the Solana Actions spec. SAP MCP context: Protocol blinks; operation class read. Use for Solana Actions and Blinks metadata fetch, validation, and POST action preparation. Preview and validate actions before signing or submitting transactions through SAP transaction tools. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    Domain to check for actions.json (e.g. "jupiter.exchange")

  Exemple d'appel

  {"name": "blinks_validateActionsJson", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• bridging_bridgeDeBridge≈ 864 tokens

  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. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (8)

  Paramètres

  • amount · string · requis
    Amount to bridge (raw)
  • sender · string · requis
    Sender address
  • tokenIn · string · requis
    Token address on source chain
  • tokenOut · string · requis
    Token address on destination chain (use "0x0" for native)
  • recipient · string · requis
    Recipient address on destination chain
  • slippageBps · number · optionnel
    Slippage tolerance in bps
  • sourceChain · number · requis
    Source chain ID (e.g. 7565164 for Solana)
  • destinationChain · number · requis
    Destination chain ID

  Exemple d'appel

  {"name": "bridging_bridgeDeBridge", "arguments": {"amount": "texte", "sender": "texte", "tokenIn": "texte", "tokenOut": "texte", "recipient": "texte", "sourceChain": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• bridging_bridgeDeBridgeStatus≈ 584 tokens

  Check the status of a deBridge DLN cross-chain transfer. SAP MCP context: Protocol bridging; operation class read. Use to check deBridge transfer status after a bridge submission. Call this after bridging_bridgeDeBridge and keep the resulting status with the user-facing bridge audit trail. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • orderId · string · requis
    deBridge DLN order ID

  Exemple d'appel

  {"name": "bridging_bridgeDeBridgeStatus", "arguments": {"orderId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• bridging_bridgeWormhole≈ 848 tokens

  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. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (7)

  Paramètres

  • token · string · requis
    Token address on source chain
  • amount · string · requis
    Amount to bridge (raw, smallest unit)
  • sender · string · requis
    Sender wallet on source chain
  • recipient · string · requis
    Recipient address on destination chain
  • relayerFee · string · optionnel
    Raw token amount (smallest unit, no decimals)
  • sourceChain · string · requis
    Source chain identifier (e.g. "solana", "ethereum", "base", "polygon")
  • destinationChain · string · requis
    Destination chain identifier

  Exemple d'appel

  {"name": "bridging_bridgeWormhole", "arguments": {"token": "texte", "amount": "texte", "sender": "texte", "recipient": "texte", "sourceChain": "texte", "destinationChain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• bridging_bridgeWormholeStatus≈ 623 tokens

  Check the status of a Wormhole bridge transfer. SAP MCP context: Protocol bridging; operation class read. Use to check Wormhole bridge transfer status after a bridge submission. Call this after bridging_bridgeWormhole and keep the resulting status with the user-facing bridge audit trail. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • sequence · string · requis
    Wormhole sequence number from bridgeWormhole response
  • sourceChain · string · requis
    Source Chain parameter for Bridging Bridge Wormhole Status.

  Exemple d'appel

  {"name": "bridging_bridgeWormholeStatus", "arguments": {"sequence": "texte", "sourceChain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• coingecko_getOHLCV≈ 658 tokens

  Get OHLCV (price chart) data from CoinGecko. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • days · string · optionnel · 1 | 7 | 14 | 30 | 90 | 180 | 365 | max
    Days parameter for Coingecko Get O H L C V.
  • tokenId · string · requis
    Token ID mint, symbol, or token identifier used by Coingecko Get O H L C V.
  • vsCurrency · string · optionnel
    Vs Currency parameter for Coingecko Get O H L C V.

  Exemple d'appel

  {"name": "coingecko_getOHLCV", "arguments": {"tokenId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• coingecko_getPoolsByToken≈ 655 tokens

  Get all liquidity pools for a token from CoinGecko on-chain DEX tracker. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • page · number · optionnel
    Page pagination control for Coingecko Get Pools By Token.
  • network · string · optionnel
    Network Solana network or cluster selector for Coingecko Get Pools By Token.
  • tokenAddress · string · requis
    Token contract/mint address

  Exemple d'appel

  {"name": "coingecko_getPoolsByToken", "arguments": {"tokenAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• coingecko_getTokenInfo≈ 591 tokens

  Get detailed token information from CoinGecko (description, links, market data). SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • tokenId · string · requis
    CoinGecko token ID

  Exemple d'appel

  {"name": "coingecko_getTokenInfo", "arguments": {"tokenId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• coingecko_getTokenPrice≈ 630 tokens

  Get token price and market data from CoinGecko. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (5)

  Paramètres

  • tokenId · string · requis
    CoinGecko token ID or contract address
  • vsCurrency · string · optionnel
    Vs Currency parameter for Coingecko Get Token Price.
  • include24hChange · boolean · optionnel
    Include24h Change parameter for Coingecko Get Token Price.
  • include24hVolume · boolean · optionnel
    Include24h Volume parameter for Coingecko Get Token Price.
  • includeMarketCap · boolean · optionnel
    Include Market Cap parameter for Coingecko Get Token Price.

  Exemple d'appel

  {"name": "coingecko_getTokenPrice", "arguments": {"tokenId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• coingecko_getTopGainersLosers≈ 633 tokens

  Get top gainers and losers from CoinGecko. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • duration · string · optionnel · 1h | 24h | 7d | 14d | 30d | 1y
    Duration parameter for Coingecko Get Top Gainers Losers.
  • vsCurrency · string · optionnel
    Vs Currency parameter for Coingecko Get Top Gainers Losers.

  Exemple d'appel

  {"name": "coingecko_getTopGainersLosers", "arguments": {"duration": "1h", "vsCurrency": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• coingecko_getTrending≈ 557 tokens

  Get trending tokens and NFTs on CoinGecko. SAP MCP context: Protocol coingecko; operation class read. Use for off-chain market data such as token prices, trending assets, token info, pools, and OHLCV. Use market data as advisory context. On-chain SAP settlement and escrow state remain authoritative for payments. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "coingecko_getTrending", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• das_getAsset≈ 573 tokens

  Get detailed information about a single NFT/asset via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Asset mint address

  Exemple d'appel

  {"name": "das_getAsset", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• das_getAssetsByCollection≈ 652 tokens

  Get all NFTs in a collection via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • page · number · optionnel
    Page pagination control for Das Get Assets By Collection.
  • limit · number · optionnel
    Limit controlling the maximum number of results returned by Das Get Assets By Collection.
  • collectionAddress · string · requis
    NFT mint address (base58)

  Exemple d'appel

  {"name": "das_getAssetsByCollection", "arguments": {"collectionAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• das_getAssetsByCreator≈ 679 tokens

  Get all NFTs/assets created by a specific creator via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (4)

  Paramètres

  • page · number · optionnel
    Page pagination control for Das Get Assets By Creator.
  • limit · number · optionnel
    Limit controlling the maximum number of results returned by Das Get Assets By Creator.
  • onlyVerified · boolean · optionnel
    Only Verified parameter for Das Get Assets By Creator.
  • creatorAddress · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "das_getAssetsByCreator", "arguments": {"creatorAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• das_getAssetsByOwner≈ 732 tokens

  Get all NFTs/assets owned by a wallet via DAS (supports pagination). SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (6)

  Paramètres

  • page · number · optionnel
    Page pagination control for Das Get Assets By Owner.
  • after · string · optionnel
    After parameter for Das Get Assets By Owner.
  • limit · number · optionnel
    Limit controlling the maximum number of results returned by Das Get Assets By Owner.
  • before · string · optionnel
    Before parameter for Das Get Assets By Owner.
  • sortBy · string · optionnel · created | updated | recent_action
    Sort By parameter for Das Get Assets By Owner.
  • ownerAddress · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "das_getAssetsByOwner", "arguments": {"ownerAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• das_searchAssets≈ 765 tokens

  Search NFTs/assets with flexible filters via DAS. SAP MCP context: Protocol das; operation class read. Use for read-only DAS NFT and asset discovery by owner, creator, collection, or search query. Prefer DAS reads before Metaplex writes when validating existing assets for an agent profile, collection, or metadata update. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (9)

  Paramètres

  • page · number · optionnel
    Page pagination control for Das Search Assets.
  • burnt · boolean · optionnel
    Burnt parameter for Das Search Assets.
  • limit · number · optionnel
    Limit controlling the maximum number of results returned by Das Search Assets.
  • frozen · boolean · optionnel
    Frozen parameter for Das Search Assets.
  • jsonUri · string · optionnel
    Json URI parameter for Das Search Assets.
  • grouping · ? · optionnel
    Grouping key-value pair (e.g. ["collection", "mint_address"])
  • compressed · boolean · optionnel
    Compressed parameter for Das Search Assets.
  • ownerAddress · string · optionnel
    Solana public key (base58)
  • creatorAddress · string · optionnel
    Solana public key (base58)

  Exemple d'appel

  {"name": "das_searchAssets", "arguments": {"page": 1, "burnt": true, "limit": 1, "frozen": true, "jsonUri": "texte", "grouping": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• gibwork_createBounty≈ 754 tokens

  Create a new bounty on Gib Work with on-chain escrow. SAP MCP context: Protocol gibwork; operation class write. Use for bounty creation, listing, and work submission. Confirm scope, payout, recipient, and deliverable evidence before writes. Use SAP attestation or feedback tools after work completion when reputation should be recorded on SAP. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (7)

  Paramètres

  • tags · array · optionnel
    Tags parameter for Gibwork Create Bounty.
  • title · string · requis
    Bounty title
  • creator · string · requis
    Solana public key (base58)
  • deadline · number · optionnel
    Deadline (Unix timestamp)
  • rewardMint · string · optionnel
    Token mint address (base58)
  • description · string · requis
    Detailed bounty description
  • rewardAmount · string · requis
    Reward amount

  Exemple d'appel

  {"name": "gibwork_createBounty", "arguments": {"title": "texte", "creator": "texte", "description": "texte", "rewardAmount": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• gibwork_listBounties≈ 673 tokens

  List available bounties on Gib Work. SAP MCP context: Protocol gibwork; operation class write. Use for bounty creation, listing, and work submission. Confirm scope, payout, recipient, and deliverable evidence before writes. Use SAP attestation or feedback tools after work completion when reputation should be recorded on SAP. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • tags · array · optionnel
    Tags parameter for Gibwork List Bounties.
  • limit · number · optionnel
    Limit controlling the maximum number of results returned by Gibwork List Bounties.
  • status · string · optionnel · open | in_progress | completed | cancelled
    Status parameter for Gibwork List Bounties.

  Exemple d'appel

  {"name": "gibwork_listBounties", "arguments": {"tags": [], "limit": 1, "status": "open"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• gibwork_submitWork≈ 681 tokens

  Submit completed work for a Gib Work bounty. SAP MCP context: Protocol gibwork; operation class write. Use for bounty creation, listing, and work submission. Confirm scope, payout, recipient, and deliverable evidence before writes. Use SAP attestation or feedback tools after work completion when reputation should be recorded on SAP. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (4)

  Paramètres

  • notes · string · optionnel
    Notes parameter for Gibwork Submit Work.
  • wallet · string · requis
    Solana public key (base58)
  • bountyId · string · requis
    Bounty ID parameter for Gibwork Submit Work.
  • submissionUrl · string · requis
    URL to the completed work (PR, doc, etc.)

  Exemple d'appel

  {"name": "gibwork_submitWork", "arguments": {"wallet": "texte", "bountyId": "texte", "submissionUrl": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jito_getBundleStatus≈ 593 tokens

  Check the status of a submitted Jito bundle. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • bundleId · string · requis
    Bundle ID parameter for Jito Get Bundle Status.

  Exemple d'appel

  {"name": "jito_getBundleStatus", "arguments": {"bundleId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jito_getTipEstimate≈ 569 tokens

  Get current Jito tip percentile estimates for bundle inclusion priority. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "jito_getTipEstimate", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jito_sendBundle≈ 659 tokens

  Send a Jito bundle for MEV-protected, atomic transaction execution. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • tipLamports · string · optionnel
    Raw token amount (smallest unit)
  • transactions · array · requis
    Array of base64-encoded signed transactions (max 5)

  Exemple d'appel

  {"name": "jito_sendBundle", "arguments": {"transactions": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_cancelDCA≈ 673 tokens

  Create an unsigned transaction to cancel a DCA recurring order. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (4)

  Paramètres

  • user · string · requis
    Wallet that owns the DCA order
  • order · string · requis
    DCA order public key to cancel
  • recurringType · string · requis · time | price
    Recurring order type — "time" for time-based DCA, "price" for price-triggered
  • computeUnitPrice · string · optionnel
    Compute Unit Price parameter for Jupiter Cancel D C A.

  Exemple d'appel

  {"name": "jupiter_cancelDCA", "arguments": {"user": "texte", "order": "texte", "recurringType": "time"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_cancelLimitOrder≈ 636 tokens

  Create an unsigned transaction to cancel a specific limit order. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • maker · string · requis
    Solana wallet public key (base58)
  • order · string · requis
    Order public key to cancel
  • computeUnitPrice · string · optionnel
    Compute Unit Price parameter for Jupiter Cancel Limit Order.

  Exemple d'appel

  {"name": "jupiter_cancelLimitOrder", "arguments": {"maker": "texte", "order": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_cancelLimitOrders≈ 666 tokens

  Create unsigned transactions to cancel multiple limit orders in batch. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • maker · string · requis
    Solana wallet public key (base58)
  • orders · array · requis
    Array of order public keys to cancel
  • computeUnitPrice · string · optionnel
    Compute Unit Price parameter for Jupiter Cancel Limit Orders.

  Exemple d'appel

  {"name": "jupiter_cancelLimitOrders", "arguments": {"maker": "texte", "orders": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_createDCA≈ 813 tokens

  Create a Dollar-Cost Averaging (DCA) recurring order. Returns an unsigned transaction. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (10)

  Paramètres

  • user · string · requis
    Wallet executing the DCA
  • payer · string · requis
    Wallet paying for the DCA setup
  • startAt · string · optionnel
    ISO 8601 start timestamp (default: now)
  • frequency · string · requis · hourly | daily | weekly | monthly | yearly
    DCA interval
  • inputMint · string · requis
    Token mint address (base58)
  • outputMint · string · requis
    Token mint address (base58)
  • totalInAmount · string · requis
    Total amount of input token to DCA
  • numberOfOrders · number · requis
    Total number of orders to split into
  • maxOutAmountPerOrder · string · optionnel
    Raw token amount as string (no decimals)
  • minOutAmountPerOrder · string · optionnel
    Raw token amount as string (no decimals)

  Exemple d'appel

  {"name": "jupiter_createDCA", "arguments": {"user": "texte", "payer": "texte", "frequency": "hourly", "inputMint": "texte", "outputMint": "texte", "totalInAmount": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_createLimitOrder≈ 766 tokens

  Create a limit order. Returns an unsigned transaction — sign and submit via executeTrigger. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (9)

  Paramètres

  • maker · string · requis
    Wallet address of the order creator
  • payer · string · requis
    Wallet paying for transaction fees
  • feeBps · number · optionnel
    Referral fee in bps
  • expiredAt · string · optionnel
    ISO 8601 expiry timestamp
  • inputMint · string · requis
    Input token mint
  • outputMint · string · requis
    Output token mint
  • makingAmount · string · requis
    Amount of input token to sell
  • takingAmount · string · requis
    Amount of output token to receive
  • computeUnitPrice · string · optionnel
    Priority fee (µ-lamports/CU)

  Exemple d'appel

  {"name": "jupiter_createLimitOrder", "arguments": {"maker": "texte", "payer": "texte", "inputMint": "texte", "outputMint": "texte", "makingAmount": "texte", "takingAmount": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_executeDCA≈ 610 tokens

  Submit a signed DCA order creation/cancellation transaction. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • requestId · string · requis
    Request ID from createDCA response
  • signedTransaction · string · requis
    Base64-encoded signed transaction

  Exemple d'appel

  {"name": "jupiter_executeDCA", "arguments": {"requestId": "texte", "signedTransaction": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_executeOrder≈ 616 tokens

  Execute a signed swap transaction obtained from getOrder and receive execution status. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • requestId · string · requis
    requestId from getOrder response
  • signedTransaction · string · requis
    Base64-encoded signed transaction

  Exemple d'appel

  {"name": "jupiter_executeOrder", "arguments": {"requestId": "texte", "signedTransaction": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_executeTrigger≈ 615 tokens

  Submit a signed limit-order transaction for on-chain execution. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • requestId · string · requis
    Request ID from createLimitOrder response
  • signedTransaction · string · requis
    Base64-encoded signed transaction

  Exemple d'appel

  {"name": "jupiter_executeTrigger", "arguments": {"requestId": "texte", "signedTransaction": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_getDCAOrders≈ 815 tokens

  Get all DCA orders (active and optionally historical) for a wallet. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (8)

  Paramètres

  • page · number · optionnel
    Page pagination control for Jupiter Get D C A Orders.
  • user · string · requis
    Wallet address to query (sent as "user" query param to Jupiter)
  • limit · number · optionnel
    Limit controlling the maximum number of results returned by Jupiter Get D C A Orders.
  • inputMint · string · optionnel
    Token mint address (base58)
  • outputMint · string · optionnel
    Token mint address (base58)
  • orderStatus · string · requis · active | history
    Filter by order status: "active" for running orders, "history" for completed/cancelled
  • recurringType · string · requis · time | price | all
    Recurring order type — "time" for time-based DCA, "price" for price-triggered, "all" for both
  • includeFailedTx · boolean · optionnel
    Include failed transactions in results (default: false)

  Exemple d'appel

  {"name": "jupiter_getDCAOrders", "arguments": {"user": "texte", "orderStatus": "active", "recurringType": "time"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_getHoldings≈ 617 tokens

  Fetch token balances and holdings for specific token accounts, including USD valuations. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • tokenAccountAddresses · array · requis
    Array of token account addresses to query balances for

  Exemple d'appel

  {"name": "jupiter_getHoldings", "arguments": {"tokenAccountAddresses": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_getLimitOrders≈ 725 tokens

  Get all limit orders (active and optionally historical) for a wallet. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (6)

  Paramètres

  • page · number · optionnel
    Page pagination control for Jupiter Get Limit Orders.
  • limit · number · optionnel
    Limit controlling the maximum number of results returned by Jupiter Get Limit Orders.
  • wallet · string · requis
    Wallet address to query
  • inputMint · string · optionnel
    Token mint address (base58)
  • outputMint · string · optionnel
    Token mint address (base58)
  • orderStatus · string · requis · active | history
    Filter by order status: "active" for open orders, "history" for filled/cancelled

  Exemple d'appel

  {"name": "jupiter_getLimitOrders", "arguments": {"wallet": "texte", "orderStatus": "active"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_getOrder≈ 704 tokens

  Get a quote + unsigned swap transaction in a single call (Ultra API). The recommended entry-point for swaps. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (7)

  Paramètres

  • taker · string · requis
    Taker (sender) wallet address
  • amount · string · requis
    Raw token amount as string (no decimals)
  • inputMint · string · requis
    Token mint address (base58)
  • outputMint · string · requis
    Token mint address (base58)
  • slippageBps · number · optionnel
    Slippage tolerance in bps (e.g. 50 = 0.5%)
  • referralFeeBps · number · optionnel
    Referral fee in bps
  • referralAccount · string · optionnel
    Solana wallet public key (base58)

  Exemple d'appel

  {"name": "jupiter_getOrder", "arguments": {"taker": "texte", "amount": "texte", "inputMint": "texte", "outputMint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_getPrice≈ 596 tokens

  Get real-time heuristic prices for tokens. Supports buy/sell price, confidence, and depth info. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. Parameter aliases accepted by SAP MCP: mint/id/token/address -> ids[0]. Prefer canonical ids: string[] in new calls. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • ids · array · requis
    Token mints to price
  • vsToken · string · optionnel
    Token mint address (base58)
  • showExtraInfo · boolean · optionnel
    Include confidence, depth, timestamps

  Exemple d'appel

  {"name": "jupiter_getPrice", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_getQuote≈ 839 tokens

  Get an optimally-routed swap quote with full route plan details (Metis engine). SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (11)

  Paramètres

  • amount · string · requis
    Raw token amount as string (no decimals)
  • swapMode · string · optionnel · ExactIn | ExactOut
    Swap Mode parameter for Jupiter Get Quote.
  • inputMint · string · requis
    Token mint address (base58)
  • outputMint · string · requis
    Token mint address (base58)
  • maxAccounts · number · optionnel
    Max accounts in transaction (default 64)
  • slippageBps · number · optionnel
    Slippage tolerance in bps (e.g. 50 = 0.5%)
  • platformFeeBps · number · optionnel
    Platform fee in bps
  • dynamicSlippage · boolean · optionnel
    Dynamic Slippage pagination control for Jupiter Get Quote.
  • onlyDirectRoutes · boolean · optionnel
    Restrict to single-hop routes
  • asLegacyTransaction · boolean · optionnel
    Return a legacy transaction
  • restrictIntermediateTokens · boolean · optionnel
    Restrict Intermediate Tokens mint, symbol, or token identifier used by Jupiter Get Quote.

  Exemple d'appel

  {"name": "jupiter_getQuote", "arguments": {"amount": "texte", "inputMint": "texte", "outputMint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_getTokenInfo≈ 607 tokens

  Search for token information by mint address, symbol, or name. Returns detailed metadata, price, organic score, and audit info. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    Search by mint address, symbol, or name. Comma-separate for multiple (max 100)

  Exemple d'appel

  {"name": "jupiter_getTokenInfo", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_getTokenList≈ 596 tokens

  Get Jupiter tokens by tag ("verified" or "lst"). Returns token metadata, organic score, price, and audit info. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · optionnel · verified | lst
    Tag to filter by — "verified" or "lst"

  Exemple d'appel

  {"name": "jupiter_getTokenList", "arguments": {"query": "verified"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_programLabels≈ 562 tokens

  Get a mapping from program ID to human-readable label for all DEX programs in the routing engine. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "jupiter_programLabels", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_searchTokens≈ 588 tokens

  Search for tokens by symbol, name, or mint address. Returns matching tokens with metadata. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    Search by token symbol, name, or mint address

  Exemple d'appel

  {"name": "jupiter_searchTokens", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_shield≈ 595 tokens

  Check token mints for potential security risks (honeypot, freeze authority, low liquidity, etc.). SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • mints · array · requis
    Token mints to check

  Exemple d'appel

  {"name": "jupiter_shield", "arguments": {"mints": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_smartSwap≈ 1077 tokens

  Smart Swap — all-in-one compound tool that fetches a quote and builds swap instructions in a single call. Provide input/output mints, amount, and wallet address to get back a quote, individual swap instructions, and a human-readable summary. The returned instructions can be assembled into a transaction and signed. This is the recommended entry-point for AI agents preparing a swap. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (17)

  Paramètres

  • amount · string · requis
    Raw token amount to swap (in smallest unit, no decimals)
  • swapMode · string · optionnel · ExactIn | ExactOut
    Swap mode (default: ExactIn)
  • inputMint · string · requis
    Source token mint address
  • feeAccount · string · optionnel
    Solana wallet public key (base58)
  • outputMint · string · requis
    Destination token mint address
  • maxAccounts · number · optionnel
    Max accounts in transaction (default: 64)
  • slippageBps · number · optionnel
    Slippage tolerance in bps (e.g. 50 = 0.5%)
  • userPublicKey · string · requis
    Wallet public key that will sign the transaction
  • platformFeeBps · number · optionnel
    Platform fee in bps for referral revenue
  • dynamicSlippage · boolean · optionnel
    Enable dynamic slippage for better execution
  • onlyDirectRoutes · boolean · optionnel
    Restrict to single-hop routes for lower latency
  • wrapAndUnwrapSol · boolean · optionnel
    Auto wrap/unwrap SOL (default: true)
  • asLegacyTransaction · boolean · optionnel
    Return a legacy transaction instead of v0
  • destinationTokenAccount · string · optionnel
    Solana wallet public key (base58)
  • dynamicComputeUnitLimit · boolean · optionnel
    Use dynamic compute unit limit based on simulation
  • restrictIntermediateTokens · boolean · optionnel
    Restrict intermediate tokens to reduce risk
  • computeUnitPriceMicroLamports · number · optionnel
    Priority fee in micro-lamports per compute unit

  Exemple d'appel

  {"name": "jupiter_smartSwap", "arguments": {"amount": "texte", "inputMint": "texte", "outputMint": "texte", "userPublicKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_swap≈ 920 tokens

  Build an unsigned swap transaction from a quote response. Sign and send the returned transaction. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (12)

  Paramètres

  • feeAccount · string · optionnel
    Solana wallet public key (base58)
  • quoteResponse · object · requis
    The full quoteResponse object from getQuote
  • userPublicKey · string · requis
    Solana wallet public key (base58)
  • useTokenLedger · boolean · optionnel
    Use Token Ledger mint, symbol, or token identifier used by Jupiter Swap.
  • dynamicSlippage · boolean · optionnel
    Dynamic Slippage pagination control for Jupiter Swap.
  • wrapAndUnwrapSol · boolean · optionnel
    Auto wrap/unwrap SOL (default true)
  • useSharedAccounts · boolean · optionnel
    Use Shared Accounts parameter for Jupiter Swap.
  • asLegacyTransaction · boolean · optionnel
    As Legacy Transaction transaction payload used by Jupiter Swap.
  • destinationTokenAccount · string · optionnel
    Solana wallet public key (base58)
  • dynamicComputeUnitLimit · boolean · optionnel
    Dynamic Compute Unit Limit controlling the maximum number of results returned by Jupiter Swap.
  • skipUserAccountsRpcCalls · boolean · optionnel
    Skip User Accounts RPC Calls endpoint or RPC selector used by Jupiter Swap.
  • computeUnitPriceMicroLamports · number · optionnel
    Priority fee in µ-lamports/CU

  Exemple d'appel

  {"name": "jupiter_swap", "arguments": {"quoteResponse": {}, "userPublicKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_swapInstructions≈ 893 tokens

  Get individual swap instructions instead of a full transaction. Useful for composing with other instructions. SAP MCP context: Jupiter protocol tools are served as AgentKit ecosystem tools. Use them for quote, route, and swap preparation, then use SAP transaction preview/sign/submit tools when an unsigned transaction must pass MCP signer policy. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (10)

  Paramètres

  • feeAccount · string · optionnel
    Solana wallet public key (base58)
  • quoteResponse · object · requis
    The full quoteResponse object from getQuote
  • userPublicKey · string · requis
    Solana wallet public key (base58)
  • useTokenLedger · boolean · optionnel
    Use Token Ledger mint, symbol, or token identifier used by Jupiter Swap Instructions.
  • wrapAndUnwrapSol · boolean · optionnel
    Wrap And Unwrap Sol parameter for Jupiter Swap Instructions.
  • useSharedAccounts · boolean · optionnel
    Use Shared Accounts parameter for Jupiter Swap Instructions.
  • asLegacyTransaction · boolean · optionnel
    As Legacy Transaction transaction payload used by Jupiter Swap Instructions.
  • destinationTokenAccount · string · optionnel
    Solana wallet public key (base58)
  • dynamicComputeUnitLimit · boolean · optionnel
    Dynamic Compute Unit Limit controlling the maximum number of results returned by Jupiter Swap Instructions.
  • computeUnitPriceMicroLamports · number · optionnel
    Compute Unit Price Micro Lamports value to use for Jupiter Swap Instructions.

  Exemple d'appel

  {"name": "jupiter_swapInstructions", "arguments": {"quoteResponse": {}, "userPublicKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_universal_deposit_chains≈ 518 tokens

  List all chains supported by Jupiter Universal Deposit for cross-chain transfers to Solana. Returns chain IDs, names, and popular chains. Free read. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "jupiter_universal_deposit_chains", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_universal_deposit_quote≈ 729 tokens

  Jupiter Universal Deposit: generate a deposit address to bridge funds from any EVM chain (Ethereum, Base, Arbitrum, etc.) to Solana USDC. Powered by Relay.link — same infrastructure as jup.ag/deposit. The user sends a normal transfer to the deposit address and receives USDC on Solana automatically. Flat $0.30 fee. Free read. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (4)

  Paramètres

  • amount · string · requis
    Amount in smallest unit (wei for ETH). Required.
  • recipient · string · requis
    Solana wallet address (base58) that will receive USDC.
  • originChainId · number · requis · 1 | 10 | 56 | 137 | 42161 | 8453 | 43114
    Origin chain ID: 1 (Ethereum), 8453 (Base), 42161 (Arbitrum), 10 (Optimism), 137 (Polygon), 56 (BSC).
  • originCurrency · string · optionnel
    Origin token address. 0x0000000000000000000000000000000000000000 for native ETH. Default: native.

  Exemple d'appel

  {"name": "jupiter_universal_deposit_quote", "arguments": {"amount": "texte", "recipient": "texte", "originChainId": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• jupiter_universal_deposit_status≈ 554 tokens

  Track a Jupiter Universal Deposit cross-chain transfer. Returns status (pending/success/failed), transaction hashes. Use requestId from jupiter_universal_deposit_quote. Free read. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • requestId · string · requis
    Request ID from the deposit quote.

  Exemple d'appel

  {"name": "jupiter_universal_deposit_status", "arguments": {"requestId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• lulo_deposit≈ 646 tokens

  Deposit into the best APR lending protocol via Lulo aggregator. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • mint · string · requis
    Token to deposit (e.g. USDC)
  • amount · string · requis
    Raw token amount (smallest unit)
  • wallet · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "lulo_deposit", "arguments": {"mint": "texte", "amount": "texte", "wallet": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• lulo_getBestRates≈ 582 tokens

  Get the best lending/yield rates across all protocols via Lulo. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • mint · string · optionnel
    Token mint address (base58)

  Exemple d'appel

  {"name": "lulo_getBestRates", "arguments": {"mint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• lulo_getPositions≈ 583 tokens

  Get all Lulo lending positions for a wallet. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "lulo_getPositions", "arguments": {"wallet": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• lulo_withdraw≈ 640 tokens

  Withdraw from Lulo lending position. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • mint · string · requis
    Token mint address (base58)
  • amount · string · requis
    Raw token amount (smallest unit)
  • wallet · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "lulo_withdraw", "arguments": {"mint": "texte", "amount": "texte", "wallet": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_balance≈ 478 tokens

  Read the base-chain SPL token balance for an address (public, no auth required).. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • mint · string · requis
    SPL mint pubkey
  • address · string · requis
    Owner wallet pubkey
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL

  Exemple d'appel

  {"name": "magicblock_balance", "arguments": {"mint": "texte", "address": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_challenge≈ 542 tokens

  Generate a challenge string for the wallet to sign (step 1 of the PER auth flow).. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • pubkey · string · requis
    Wallet pubkey that will sign the challenge
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL

  Exemple d'appel

  {"name": "magicblock_challenge", "arguments": {"pubkey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_deposit≈ 796 tokens

  Build an unsigned transaction to deposit SPL tokens from Solana into an Ephemeral Rollup. Then use sap_preview_transaction, sap_sign_transaction, and sap_submit_signed_transaction — or use sap_payments_finalize_transaction for 1-call preview+sign+submit (hosted mode). Do not create local signing scripts. Builder fee applies. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (9)

  Paramètres

  • mint · string · optionnel
    SPL mint. Defaults to USDC (mainnet) or devnet USDC
  • owner · string · requis
    Wallet pubkey that owns the tokens and will sign
  • amount · number · requis
    Base-unit amount to deposit (integer, minimum 1)
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • validator · string · optionnel
    Optional ER validator pubkey. Defaults to the selected ephemeral RPC identity.
  • idempotent · boolean · optionnel
    Use idempotent variants for preparatory init instructions (default true)
  • initIfMissing · boolean · optionnel
    Initialize the transfer queue if missing (default true)
  • initAtasIfMissing · boolean · optionnel
    Initialize associated token accounts if missing (default true)
  • initVaultIfMissing · boolean · optionnel
    Initialize the vault if missing (default true)

  Exemple d'appel

  {"name": "magicblock_deposit", "arguments": {"owner": "texte", "amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_ensureCrank≈ 658 tokens

  Force a transfer queue crank attempt for a mint. Use this after a private transfer or private swap if the Hydra delivery crank has not yet delivered funds to the recipient. The API verifies the validator-scoped transfer queue and forces one crank attempt, returning the crank signature. Read-only tier: this does not move funds, it triggers the existing queued delivery.. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • mint · string · requis
    SPL mint to crank the transfer queue for
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • validator · string · optionnel
    Optional ER validator pubkey. Defaults to the well-known MagicBlock validator (MAS1Dt9qreoRMQ14YQuhg8UTZMMzDdKhmkZMECCzk57)

  Exemple d'appel

  {"name": "magicblock_ensureCrank", "arguments": {"mint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_getAccountInfo≈ 584 tokens

  Fetch account information (data, lamports, owner, executable, space) via the Magic Router.. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • account · string · requis
    Account pubkey to fetch info for
  • encoding · string · optionnel · base64 | base64+zstd
    Encoding for account data
  • endpoint · string · optionnel · mainnet | devnet
    MagicBlock Router endpoint: 'mainnet' or 'devnet'

  Exemple d'appel

  {"name": "magicblock_getAccountInfo", "arguments": {"account": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_getBlockhashForAccounts≈ 581 tokens

  Get a blockhash and last valid block height for a batch of account addresses (max 100).. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • accounts · array · requis
    Array of account addresses (max 100)
  • endpoint · string · optionnel · mainnet | devnet
    MagicBlock Router endpoint: 'mainnet' or 'devnet'

  Exemple d'appel

  {"name": "magicblock_getBlockhashForAccounts", "arguments": {"accounts": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_getDelegationStatus≈ 573 tokens

  Check whether a Solana account is delegated to an Ephemeral Rollup. Returns authority, owner, delegation slot, and lamports.. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • account · string · requis
    Account pubkey to check delegation status for
  • endpoint · string · optionnel · mainnet | devnet
    MagicBlock Router endpoint: 'mainnet' or 'devnet'

  Exemple d'appel

  {"name": "magicblock_getDelegationStatus", "arguments": {"account": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_getIdentity≈ 519 tokens

  Get the identity and FQDN of the current ER Validator node.. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • endpoint · string · optionnel · mainnet | devnet
    MagicBlock Router endpoint: 'mainnet' or 'devnet'

  Exemple d'appel

  {"name": "magicblock_getIdentity", "arguments": {"endpoint": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_getRandomnessResult≈ 590 tokens

  Check whether a VRF request has been fulfilled by reading the RandomnessRequest account on-chain. Returns fulfilled status, random bytes (if available), and the request metadata.. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • endpoint · string · optionnel · mainnet | devnet
    MagicBlock Router endpoint: 'mainnet' or 'devnet'
  • requestKey · string · requis
    VRF request PDA key from magicblock_requestRandomness

  Exemple d'appel

  {"name": "magicblock_getRandomnessResult", "arguments": {"requestKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_getRoutes≈ 520 tokens

  List available Ephemeral Rollup nodes from the Magic Router (identity, FQDN, fee, block time, country).. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • endpoint · string · optionnel · mainnet | devnet
    MagicBlock Router endpoint: 'mainnet' or 'devnet'

  Exemple d'appel

  {"name": "magicblock_getRoutes", "arguments": {"endpoint": "mainnet"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_getSignatureStatuses≈ 585 tokens

  Check the confirmation status (processed/confirmed/finalized) of one or more transaction signatures.. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • endpoint · string · optionnel · mainnet | devnet
    MagicBlock Router endpoint: 'mainnet' or 'devnet'
  • signatures · array · requis
    Array of transaction signatures

  Exemple d'appel

  {"name": "magicblock_getSignatureStatuses", "arguments": {"signatures": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_health≈ 482 tokens

  Check the health status of the MagicBlock Private Payments API.. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "magicblock_health", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_initializeMint≈ 636 tokens

  Build an unsigned transaction that initializes a validator-scoped transfer queue for a mint. Then use sap_preview_transaction, sap_sign_transaction, and sap_submit_signed_transaction — or use sap_payments_finalize_transaction for 1-call preview+sign+submit (hosted mode). Builder fee applies. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (4)

  Paramètres

  • mint · string · requis
    SPL mint to initialize a transfer queue for
  • owner · string · requis
    Wallet pubkey that will sign the transaction
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • validator · string · optionnel
    Optional ER validator pubkey

  Exemple d'appel

  {"name": "magicblock_initializeMint", "arguments": {"mint": "texte", "owner": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_isMintInitialized≈ 562 tokens

  Check whether a mint has a validator-scoped transfer queue on the ephemeral RPC.. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • mint · string · requis
    SPL mint to check
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • validator · string · optionnel
    Optional ER validator pubkey

  Exemple d'appel

  {"name": "magicblock_isMintInitialized", "arguments": {"mint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_login≈ 604 tokens

  Exchange a signed challenge for a bearer token (step 2 of PER auth flow). The token is used for private-balance and private transfers.. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (4)

  Paramètres

  • pubkey · string · requis
    Wallet pubkey that signed the challenge
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • challenge · string · requis
    Challenge string from magicblock_challenge
  • signature · string · requis
    Wallet signature over the challenge string

  Exemple d'appel

  {"name": "magicblock_login", "arguments": {"pubkey": "texte", "challenge": "texte", "signature": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_privateBalance≈ 594 tokens

  Read the ephemeral-rollup SPL token balance for an address (requires bearer token from login).. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (4)

  Paramètres

  • mint · string · requis
    SPL mint pubkey
  • address · string · requis
    Owner wallet pubkey
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • authToken · string · requis
    Bearer token from magicblock_login (required for private reads)

  Exemple d'appel

  {"name": "magicblock_privateBalance", "arguments": {"mint": "texte", "address": "texte", "authToken": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_private_balance≈ 596 tokens

  Read the ephemeral-rollup SPL token balance for an address (requires bearer token from login).. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (4)

  Paramètres

  • mint · string · requis
    SPL mint pubkey
  • address · string · requis
    Owner wallet pubkey
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • authToken · string · requis
    Bearer token from magicblock_login (required for private reads)

  Exemple d'appel

  {"name": "magicblock_private_balance", "arguments": {"mint": "texte", "address": "texte", "authToken": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_requestRandomness≈ 932 tokens

  Request provably fair on-chain randomness from the MagicBlock VRF oracle (Vrf1RNUjXmQGjmQrQLvJHs9SNkvDJEsRVFPkfSQUwGz). Builds an unsigned transaction that invokes request_randomness on the VRF program. Use sap_preview_transaction, sap_sign_transaction, and sap_submit_signed_transaction; do not create local signing scripts. The oracle queue defaults to the base-layer queue (Cuj97ggrhhidhbu39TijNVqE74xvKJ69gDervRUXAxGh); set ephemeral=true to use the ER queue for delegated programs. Builder fee applies. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (7)

  Paramètres

  • payer · string · requis
    Wallet pubkey that will pay for the request and sign the transaction
  • endpoint · string · optionnel · mainnet | devnet
    MagicBlock Router endpoint: 'mainnet' or 'devnet'
  • ephemeral · boolean · optionnel
    Use the Ephemeral Rollup oracle queue instead of the base-layer queue (default false)
  • callerSeed · string · requis
    Seed string for the VRF request — committed before randomness is produced. The seed is hashed to 32 bytes.
  • callbackAccounts · array · requis
    Accounts to pass to the callback instruction
  • callbackProgramId · string · requis
    Program ID of the callback program (the program that will consume the randomness)
  • callbackDiscriminator · string · requis
    Base58 or hex discriminator for the callback instruction in your program

  Exemple d'appel

  {"name": "magicblock_requestRandomness", "arguments": {"payer": "texte", "callerSeed": "texte", "callbackAccounts": [], "callbackProgramId": "texte", "callbackDiscriminator": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_swap≈ 954 tokens

  Build an unsigned swap transaction from a quote. 'public' mode passes through Jupiter. 'private' mode routes output through a scheduled private transfer: requires destination, minDelayMs (string ms), maxDelayMs (string ms, <= 600000), and split (1-14). The API appends a schedule_private_transfer instruction that registers a one-shot Hydra crank for delivery. Legacy transactions are not allowed in private mode. Agents must continue with sap_preview_transaction, sap_sign_transaction, and sap_submit_signed_transaction; never write temporary signing scripts or read keypair JSON. Value-action fee applies. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid value-action; preview cost and transaction effects before user confirmation. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (11)

  Paramètres

  • split · number · optionnel
    Private only. Number of queue entries to split across (1-14)
  • validator · string · optionnel
    Optional validator pubkey for the transfer-queue PDA
  • maxDelayMs · string · optionnel
    Private only. Latest (ms) the queued transfer may settle (<= 600000)
  • minDelayMs · string · optionnel
    Private only. Earliest (ms) the queued transfer may settle
  • visibility · string · optionnel · public | private
    'public' = transparent Jupiter pass-through, 'private' = output routed through scheduled private transfer
  • clientRefId · string · optionnel
    Private only. Optional u64 client correlation ID
  • destination · string · optionnel
    Final private-transfer recipient (required when visibility='private')
  • quoteResponse · object · requis
    Quote response object from magicblock_swapQuote (pass as-is)
  • userPublicKey · string · requis
    Wallet that will sign the swap transaction
  • wrapAndUnwrapSol · boolean · optionnel
    Auto wrap/unwrap native SOL when needed (default true)
  • asLegacyTransaction · boolean · optionnel
    Build a legacy transaction (not allowed when visibility=private, default false)

  Exemple d'appel

  {"name": "magicblock_swap", "arguments": {"quoteResponse": {}, "userPublicKey": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_swapQuote≈ 769 tokens

  Get a swap quote between two SPL mints (proxies Triton Metis swap API). Pass the result into magicblock_swap. Lightweight read tier; use this before any value-moving swap. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (9)

  Paramètres

  • amount · string · requis
    Raw amount to swap (unsigned integer string, e.g. '1000000')
  • swapMode · string · optionnel · ExactIn | ExactOut
    Swap mode: fixed input or fixed output amount
  • inputMint · string · requis
    Input token mint address
  • outputMint · string · requis
    Output token mint address
  • maxAccounts · number · optionnel
    Approximate maximum account budget for the route (default 64)
  • slippageBps · number · optionnel
    Slippage threshold in basis points (e.g. 50 = 0.5%)
  • platformFeeBps · number · optionnel
    Optional platform fee in basis points
  • onlyDirectRoutes · boolean · optionnel
    Limit routing to a single hop (default false)
  • restrictIntermediateTokens · boolean · optionnel
    Restrict intermediate tokens to a more stable set (default false)

  Exemple d'appel

  {"name": "magicblock_swapQuote", "arguments": {"amount": "texte", "inputMint": "texte", "outputMint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_swap_quote≈ 770 tokens

  Get a swap quote between two SPL mints (proxies Triton Metis swap API). Pass the result into magicblock_swap. Lightweight read tier; use this before any value-moving swap. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (9)

  Paramètres

  • amount · string · requis
    Raw amount to swap (unsigned integer string, e.g. '1000000')
  • swapMode · string · optionnel · ExactIn | ExactOut
    Swap mode: fixed input or fixed output amount
  • inputMint · string · requis
    Input token mint address
  • outputMint · string · requis
    Output token mint address
  • maxAccounts · number · optionnel
    Approximate maximum account budget for the route (default 64)
  • slippageBps · number · optionnel
    Slippage threshold in basis points (e.g. 50 = 0.5%)
  • platformFeeBps · number · optionnel
    Optional platform fee in basis points
  • onlyDirectRoutes · boolean · optionnel
    Limit routing to a single hop (default false)
  • restrictIntermediateTokens · boolean · optionnel
    Restrict intermediate tokens to a more stable set (default false)

  Exemple d'appel

  {"name": "magicblock_swap_quote", "arguments": {"amount": "texte", "inputMint": "texte", "outputMint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_transfer≈ 1212 tokens

  Build an unsigned SPL token transfer through an Ephemeral Rollup. Use this only when private visibility or an ephemeral balance is explicitly requested. For an ordinary public base-to-base wallet transfer, use sap_build_spl_transfer instead; it detects legacy SPL versus Token-2022 from the mint on-chain. Supports delayed settlement, split transfers, and gasless mode. Then use sap_preview_transaction, sap_sign_transaction, and sap_submit_signed_transaction — or use sap_payments_finalize_transaction for 1-call preview+sign+submit (hosted mode). Builder fee applies. SAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (20)

  Paramètres

  • to · string · requis
    Recipient wallet pubkey
  • from · string · requis
    Sender wallet pubkey
  • memo · string · optionnel
    Optional memo appended to the transaction
  • mint · string · requis
    SPL mint pubkey
  • split · number · optionnel
    Private only. Number of queue entries to split across (1-15, default 1)
  • amount · number · requis
    Base-unit amount to transfer (integer, minimum 1)
  • legacy · boolean · optionnel
    Skip lookup-table compilation, return a legacy transaction (default false)
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • gasless · boolean · optionnel
    When true, uses configured sponsor as fee payer (default false)
  • authToken · string · optionnel
    Bearer token from login (required for private transfers)
  • toBalance · string · requis · base | ephemeral
    Where the recipient should receive funds
  • validator · string · optionnel
    Optional ER validator pubkey
  • maxDelayMs · string · optionnel
    Private only. Latest (ms) the queued transfer may settle (<= 600000)
  • minDelayMs · string · optionnel
    Private only. Earliest (ms) the queued transfer may settle. Default '0'
  • visibility · string · requis · public | private
    'public' = transparent SPL transfer, 'private' = routed through Private ER with delayed+split settlement
  • clientRefId · string · optionnel
    Private only. Encrypted client reference ID for payment confirmation
  • fromBalance · string · requis · base | ephemeral
    Where the sender's balance is held
  • initIfMissing · boolean · optionnel
    Initialize transfer queue if missing (default true)
  • initAtasIfMissing · boolean · optionnel
    Initialize recipient ATA if missing (default true)
  • initVaultIfMissing · boolean · optionnel
    Initialize vault if missing (default false). WARNING: when legacy=true, setting this to true can exceed the 1232-byte legacy transaction limit and produce TRANSACTION_TOO_LARGE errors. Prefer v0 (legacy=false) when vault init is needed.

  Exemple d'appel

  {"name": "magicblock_transfer", "arguments": {"to": "texte", "from": "texte", "mint": "texte", "amount": 1, "toBalance": "base", "visibility": "public"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• magicblock_withdraw≈ 760 tokens

  Build an unsigned transaction to withdraw SPL tokens from an Ephemeral Rollup back to Solana. Then use sap_preview_transaction, sap_sign_transaction, and sap_submit_signed_transaction — or use sap_payments_finalize_transaction for 1-call preview+sign+submit (hosted mode). Builder fee applies. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (9)

  Paramètres

  • mint · string · requis
    SPL mint on Solana
  • owner · string · requis
    Wallet pubkey that owns the tokens and will sign
  • amount · number · requis
    Base-unit amount to withdraw (integer, minimum 1)
  • cluster · string · optionnel
    Cluster: 'mainnet', 'devnet', or custom RPC URL
  • validator · string · optionnel
    Optional ER validator pubkey
  • idempotent · boolean · optionnel
    Use idempotent variants for preparatory init instructions (default true)
  • escrowIndex · number · optionnel
    Optional escrow index for the withdrawal
  • initIfMissing · boolean · optionnel
    Initialize transfer queue if missing (default true)
  • initAtasIfMissing · boolean · optionnel
    Initialize ATAs if missing (default true)

  Exemple d'appel

  {"name": "magicblock_withdraw", "arguments": {"mint": "texte", "owner": "texte", "amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• manifest_cancelOrder≈ 654 tokens

  Cancel a limit order on a Manifest market. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)
  • orderId · string · requis
    Order ID parameter for Manifest Cancel Order.
  • marketId · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "manifest_cancelOrder", "arguments": {"wallet": "texte", "orderId": "texte", "marketId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• manifest_createMarket≈ 628 tokens

  Create a new Manifest market for a token pair. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • creator · string · requis
    Solana public key (base58)
  • baseMint · string · requis
    Base token mint
  • quoteMint · string · requis
    Quote token mint

  Exemple d'appel

  {"name": "manifest_createMarket", "arguments": {"creator": "texte", "baseMint": "texte", "quoteMint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• manifest_getOrderbook≈ 612 tokens

  Get the current orderbook for a Manifest market. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (2)

  Paramètres

  • depth · number · optionnel
    Depth parameter for Manifest Get Orderbook.
  • marketId · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "manifest_getOrderbook", "arguments": {"marketId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• manifest_placeLimitOrder≈ 736 tokens

  Place a limit order on a Manifest market. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (6)

  Paramètres

  • side · string · requis · buy | sell
    Side parameter for Manifest Place Limit Order.
  • size · string · requis
    Order size in base tokens
  • price · number · requis
    Limit price
  • wallet · string · requis
    Solana public key (base58)
  • marketId · string · requis
    Solana public key (base58)
  • orderType · string · optionnel · limit | postOnly | ioc
    Order Type parameter for Manifest Place Limit Order.

  Exemple d'appel

  {"name": "manifest_placeLimitOrder", "arguments": {"side": "buy", "size": "texte", "price": 1, "wallet": "texte", "marketId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_configureRoyalties≈ 868 tokens

  Configure royalty fee and creator splits for an NFT. SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (4)

  Paramètres

  • mint · string · requis
    NFT mint address (base58)
  • creators · array · requis
    Creator list with revenue shares (must sum to 100)
  • updateAuthority · string · requis
    Solana public key (base58)
  • sellerFeeBasisPoints · number · requis
    Royalty fee in bps

  Exemple d'appel

  {"name": "metaplex-nft_configureRoyalties", "arguments": {"mint": "texte", "creators": [], "updateAuthority": "texte", "sellerFeeBasisPoints": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_delegateAuthority≈ 793 tokens

  Delegate a specific authority (update, mint, freeze, collection) to another wallet. SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (4)

  Paramètres

  • mint · string · requis
    NFT mint address (base58)
  • newAuthority · string · requis
    Solana public key (base58)
  • authorityType · string · requis · update | mint | freeze | collection
    Type of authority to delegate
  • currentAuthority · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "metaplex-nft_delegateAuthority", "arguments": {"mint": "texte", "newAuthority": "texte", "authorityType": "update", "currentAuthority": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_deployCollection≈ 973 tokens

  Deploy a new NFT collection via Metaplex. Returns the collection mint and metadata addresses. SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (8)

  Paramètres

  • uri · string · requis
    URI to collection metadata JSON
  • name · string · requis
    Collection name
  • symbol · string · requis
    Collection symbol
  • creators · array · optionnel
    Creator list with revenue shares (must sum to 100)
  • authority · string · requis
    Collection authority wallet
  • isMutable · boolean · optionnel
    Is Mutable parameter for Metaplex-nft Deploy Collection.
  • maxSupply · number · optionnel
    Max NFTs in collection (0 = unlimited)
  • sellerFeeBasisPoints · number · optionnel
    Royalty fee in bps (500 = 5%)

  Exemple d'appel

  {"name": "metaplex-nft_deployCollection", "arguments": {"uri": "texte", "name": "texte", "symbol": "texte", "authority": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_mintNFT≈ 1032 tokens

  Mint a new NFT via Metaplex. Supports both standard and compressed (cNFT) minting. SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (11)

  Paramètres

  • uri · string · requis
    URI to NFT metadata JSON (image, attributes, etc.)
  • name · string · requis
    NFT name
  • symbol · string · optionnel
    NFT symbol
  • creators · array · optionnel
    Creators parameter for Metaplex-nft Mint N F T.
  • authority · string · requis
    Mint authority wallet
  • isMutable · boolean · optionnel
    Is Mutable parameter for Metaplex-nft Mint N F T.
  • recipient · string · optionnel
    Solana public key (base58)
  • collection · string · optionnel
    NFT mint address (base58)
  • merkleTree · string · optionnel
    Solana public key (base58)
  • isCompressed · boolean · optionnel
    Mint as compressed NFT (cNFT) for lower cost
  • sellerFeeBasisPoints · number · optionnel
    Seller Fee Basis Points parameter for Metaplex-nft Mint N F T.

  Exemple d'appel

  {"name": "metaplex-nft_mintNFT", "arguments": {"uri": "texte", "name": "texte", "authority": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_revokeAuthority≈ 766 tokens

  Revoke (remove) a specific authority. Irreversible for some types. SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • mint · string · requis
    NFT mint address (base58)
  • authority · string · requis
    Current authority holder
  • authorityType · string · requis · update | mint | freeze | collection
    Authority Type parameter for Metaplex-nft Revoke Authority.

  Exemple d'appel

  {"name": "metaplex-nft_revokeAuthority", "arguments": {"mint": "texte", "authority": "texte", "authorityType": "update"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_setAndVerifyCollection≈ 780 tokens

  Set and verify a collection on an NFT in a single transaction. SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (4)

  Paramètres

  • mint · string · requis
    NFT mint address (base58)
  • collection · string · requis
    NFT mint address (base58)
  • updateAuthority · string · requis
    NFT update authority
  • collectionAuthority · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "metaplex-nft_setAndVerifyCollection", "arguments": {"mint": "texte", "collection": "texte", "updateAuthority": "texte", "collectionAuthority": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_updateMetadata≈ 1023 tokens

  Update NFT metadata fields (name, symbol, URI, creators, royalties, authority). SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: local-signer write workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (10)

  Paramètres

  • uri · string · optionnel
    New metadata URI
  • mint · string · requis
    NFT mint address
  • name · string · optionnel
    New name
  • symbol · string · optionnel
    New symbol
  • creators · array · optionnel
    Creators parameter for Metaplex-nft Update Metadata.
  • isMutable · boolean · optionnel
    Is Mutable parameter for Metaplex-nft Update Metadata.
  • updateAuthority · string · requis
    Current update authority
  • newUpdateAuthority · string · optionnel
    Solana public key (base58)
  • primarySaleHappened · boolean · optionnel
    Primary Sale Happened parameter for Metaplex-nft Update Metadata.
  • sellerFeeBasisPoints · number · optionnel
    Seller Fee Basis Points parameter for Metaplex-nft Update Metadata.

  Exemple d'appel

  {"name": "metaplex-nft_updateMetadata", "arguments": {"mint": "texte", "updateAuthority": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_verifyCollection≈ 738 tokens

  Verify an NFT as part of a collection. SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • mint · string · requis
    NFT mint to verify
  • collection · string · requis
    Collection mint
  • collectionAuthority · string · requis
    Collection authority wallet

  Exemple d'appel

  {"name": "metaplex-nft_verifyCollection", "arguments": {"mint": "texte", "collection": "texte", "collectionAuthority": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• metaplex-nft_verifyCreator≈ 718 tokens

  Verify a creator on an NFT's metadata (requires creator's signature). SAP MCP context: Protocol metaplex-nft; operation class write. Use for Metaplex NFT collection, mint, metadata, royalty, creator verification, collection verification, and authority workflows. Confirm metadata URI, collection mint, creators, royalties, update authority, and ownership before writes. For agent identity, plan with sap_agent_identity_plan, register the SAP on-chain profile through sap_payments_register_agent, then use agentUri or metadataUri to point at off-chain or NFT-backed metadata. Use these Metaplex tools when the agent also needs an NFT collection, badge, or verifiable media asset. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • mint · string · requis
    NFT mint address (base58)
  • creator · string · requis
    Creator wallet to verify

  Exemple d'appel

  {"name": "metaplex-nft_verifyCreator", "arguments": {"mint": "texte", "creator": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• meteora_addDLMMLiquidity≈ 772 tokens

  Add liquidity to a Meteora DLMM pool with a distribution strategy. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (7)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)
  • amountX · string · requis
    Raw token amount (smallest unit)
  • amountY · string · requis
    Raw token amount (smallest unit)
  • maxBinId · number · optionnel
    Max Bin ID parameter for Meteora Add D L M M Liquidity.
  • minBinId · number · optionnel
    Min Bin ID parameter for Meteora Add D L M M Liquidity.
  • strategy · string · optionnel · spot | curve | bid-ask
    Liquidity distribution strategy
  • poolAddress · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "meteora_addDLMMLiquidity", "arguments": {"wallet": "texte", "amountX": "texte", "amountY": "texte", "poolAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• meteora_createAlphaVault≈ 735 tokens

  Create a Meteora Alpha Vault for fair token launches with vesting. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (6)

  Paramètres

  • creator · string · requis
    Solana public key (base58)
  • startTime · number · optionnel
    Vault start time (Unix timestamp)
  • maxDeposit · string · requis
    Maximum deposit cap
  • depositMint · string · requis
    Token mint accepted for deposits
  • poolAddress · string · requis
    Solana public key (base58)
  • vestingDuration · number · requis
    Vesting duration in seconds

  Exemple d'appel

  {"name": "meteora_createAlphaVault", "arguments": {"creator": "texte", "maxDeposit": "texte", "depositMint": "texte", "poolAddress": "texte", "vestingDuration": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• meteora_createDLMMPool≈ 872 tokens

  Create a Meteora DLMM (Discrete Liquidity Market Maker) pool. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (11)

  Paramètres

  • mintX · string · requis
    Token X mint
  • mintY · string · requis
    Token Y mint
  • feeBps · number · optionnel
    Fee Bps parameter for Meteora Create D L M M Pool.
  • amountX · string · optionnel
    Raw token amount (smallest unit)
  • amountY · string · optionnel
    Raw token amount (smallest unit)
  • binStep · number · requis
    Bin step size (defines fee tier and price granularity)
  • creator · string · requis
    Solana public key (base58)
  • initialPrice · number · requis
    Initial Price parameter for Meteora Create D L M M Pool.
  • activationType · string · optionnel · slot | timestamp
    Activation Type parameter for Meteora Create D L M M Pool.
  • activationPoint · number · optionnel
    Activation Point parameter for Meteora Create D L M M Pool.
  • priceRoundingUp · boolean · optionnel
    Price Rounding Up parameter for Meteora Create D L M M Pool.

  Exemple d'appel

  {"name": "meteora_createDLMMPool", "arguments": {"mintX": "texte", "mintY": "texte", "binStep": 1, "creator": "texte", "initialPrice": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• meteora_createDynamicPool≈ 812 tokens

  Create a Meteora Dynamic AMM pool. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (9)

  Paramètres

  • mintA · string · requis
    Token mint address (base58)
  • mintB · string · requis
    Token mint address (base58)
  • amountA · string · requis
    Raw token amount (smallest unit)
  • amountB · string · requis
    Raw token amount (smallest unit)
  • creator · string · requis
    Solana public key (base58)
  • activationType · string · optionnel · slot | timestamp
    Activation Type parameter for Meteora Create Dynamic Pool.
  • activationPoint · number · optionnel
    Activation slot/timestamp
  • tradeFeeNumerator · number · optionnel
    Trade fee numerator (default pool fee)
  • tradeFeeDenominator · number · optionnel
    Trade Fee Denominator parameter for Meteora Create Dynamic Pool.

  Exemple d'appel

  {"name": "meteora_createDynamicPool", "arguments": {"mintA": "texte", "mintB": "texte", "amountA": "texte", "amountB": "texte", "creator": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• meteora_removeDLMMLiquidity≈ 670 tokens

  Remove liquidity from a Meteora DLMM position. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (3)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)
  • percentage · number · optionnel
    Percentage parameter for Meteora Remove D L M M Liquidity.
  • positionAddress · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "meteora_removeDLMMLiquidity", "arguments": {"wallet": "texte", "positionAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• openbook_cancelOrder≈ 634 tokens

  Cancel an open order on an Openbook market. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (3)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)
  • orderId · string · requis
    Order ID parameter for Openbook Cancel Order.
  • marketId · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "openbook_cancelOrder", "arguments": {"wallet": "texte", "orderId": "texte", "marketId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• openbook_createMarket≈ 676 tokens

  Create a new Openbook DEX market for a token pair. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (5)

  Paramètres

  • creator · string · requis
    Solana public key (base58)
  • lotSize · number · requis
    Minimum order size
  • baseMint · string · requis
    Token mint address (base58)
  • tickSize · number · requis
    Minimum price increment
  • quoteMint · string · requis
    Token mint address (base58)

  Exemple d'appel

  {"name": "openbook_createMarket", "arguments": {"creator": "texte", "lotSize": 1, "baseMint": "texte", "tickSize": 1, "quoteMint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• openbook_placeOrder≈ 716 tokens

  Place an order on an Openbook market. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (6)

  Paramètres

  • side · string · requis · buy | sell
    Side parameter for Openbook Place Order.
  • size · string · requis
    Raw token amount (smallest unit)
  • price · number · requis
    Price parameter for Openbook Place Order.
  • wallet · string · requis
    Solana public key (base58)
  • marketId · string · requis
    Solana public key (base58)
  • orderType · string · optionnel · limit | ioc | postOnly
    Order Type parameter for Openbook Place Order.

  Exemple d'appel

  {"name": "openbook_placeOrder", "arguments": {"side": "buy", "size": "texte", "price": 1, "wallet": "texte", "marketId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• orca_closePosition≈ 632 tokens

  Close a Whirlpool position and collect all fees/rewards. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)
  • positionMint · string · requis
    Token mint address (base58)

  Exemple d'appel

  {"name": "orca_closePosition", "arguments": {"wallet": "texte", "positionMint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• orca_collectFees≈ 628 tokens

  Collect accumulated fees from a Whirlpool position. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (2)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)
  • positionMint · string · requis
    Token mint address (base58)

  Exemple d'appel

  {"name": "orca_collectFees", "arguments": {"wallet": "texte", "positionMint": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• orca_getWhirlpool≈ 583 tokens

  Get Orca Whirlpool pool information. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

  Paramètres, retour & exemple (1)

  Paramètres

  • poolAddress · string · requis
    Whirlpool pool address

  Exemple d'appel

  {"name": "orca_getWhirlpool", "arguments": {"poolAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• orca_openPosition≈ 728 tokens

  Open a concentrated liquidity position on an Orca Whirlpool. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (6)

  Paramètres

  • wallet · string · requis
    Solana public key (base58)
  • amountA · string · optionnel
    Raw token amount (smallest unit)
  • amountB · string · optionnel
    Raw token amount (smallest unit)
  • priceLower · number · requis
    Price Lower parameter for Orca Open Position.
  • priceUpper · number · requis
    Price Upper parameter for Orca Open Position.
  • poolAddress · string · requis
    Solana public key (base58)

  Exemple d'appel

  {"name": "orca_openPosition", "arguments": {"wallet": "texte", "priceLower": 1, "priceUpper": 1, "poolAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• orca_swap≈ 711 tokens

  Swap tokens on an Orca Whirlpool. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (6)

  Paramètres

  • amount · string · requis
    Raw token amount (smallest unit)
  • wallet · string · requis
    Solana public key (base58)
  • inputMint · string · requis
    Token mint address (base58)
  • poolAddress · string · requis
    Solana public key (base58)
  • slippageBps · number · optionnel
    Slippage Bps pagination control for Orca Swap.
  • isExactInput · boolean · optionnel
    Is Exact Input parameter for Orca Swap.

  Exemple d'appel

  {"name": "orca_swap", "arguments": {"amount": "texte", "wallet": "texte", "inputMint": "texte", "poolAddress": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• pump_launchToken≈ 757 tokens

  Launch a new token on Pump.fun via PumpPortal. Optionally include an initial dev buy. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (9)

  Paramètres

  • name · string · requis
    Token name
  • image · string · optionnel
    Token logo URL
  • symbol · string · requis
    Token ticker
  • twitter · string · optionnel
    Twitter/X handle
  • website · string · optionnel
    Website URL
  • deployer · string · requis
    Deployer wallet
  • telegram · string · optionnel
    Telegram group link
  • description · string · optionnel
    Description parameter for Pump Launch Token.
  • initialBuyAmount · string · optionnel
    Raw token amount (smallest unit)

  Exemple d'appel

  {"name": "pump_launchToken", "arguments": {"name": "texte", "symbol": "texte", "deployer": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

• pump_trade≈ 697 tokens

  Buy or sell tokens on Pump.fun bonding curve. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial.

  Paramètres, retour & exemple (5)

  Paramètres

  • mint · string · requis
    Pump.fun token mint
  • action · string · requis · buy | sell
    Trade direction
  • amount · string · requis
    Amount in SOL (buy) or tokens (sell)
  • wallet · string · requis
    Solana public key (base58)
  • slippageBps · number · optionnel
    Slippage Bps pagination control for Pump Trade.

  Exemple d'appel

  {"name": "pump_trade", "arguments": {"mint": "texte", "action": "buy", "amount": "texte", "wallet": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"content": [], "isError": true}}

+ 333 autres outils (affichage limité à 120).

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.sap.oobeprotocol.ai/mcp