jupiter_getDCAOrders
InactiveTool of SAP MCP Server
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.
Parameters schema
{
"type": "object",
"required": [
"user",
"recurringType",
"orderStatus"
],
"properties": {
"page": {
"type": "number",
"description": "Page pagination control for Jupiter Get D C A Orders."
},
"user": {
"type": "string",
"description": "Wallet address to query (sent as \"user\" query param to Jupiter)"
},
"limit": {
"type": "number",
"description": "Limit controlling the maximum number of results returned by Jupiter Get D C A Orders."
},
"inputMint": {
"type": "string",
"description": "Token mint address (base58)"
},
"outputMint": {
"type": "string",
"description": "Token mint address (base58)"
},
"orderStatus": {
"enum": [
"active",
"history"
],
"type": "string",
"description": "Filter by order status: \"active\" for running orders, \"history\" for completed/cancelled"
},
"recurringType": {
"enum": [
"time",
"price",
"all"
],
"type": "string",
"description": "Recurring order type — \"time\" for time-based DCA, \"price\" for price-triggered, \"all\" for both"
},
"includeFailedTx": {
"type": "boolean",
"description": "Include failed transactions in results (default: false)"
}
},
"additionalProperties": false
}No endpoints wrapped at confidence ≥ 0.50.
Parent server
SAP MCP Server
https://github.com/OOBE-PROTOCOL/sap-mcp
2/7 registries