Call an MCP tool
JSON-RPC 2.0 endpoint for the MCP server. Set method to tools/call and params.name to one of getAccountBalance, getAccountHistory, getUserCards, getUserCardTransactions, getUserCardSummary, getUserCardBalanceMovements, getUserCardBalanceAutomation, getCardRevealPublicKey, createUserCards, updateUserCard. The last two CHANGE data (they create and modify cards) and require a key carrying the mcp:write scope; without it the call succeeds at the HTTP layer and the refusal comes back as an error tool result, not a 403. Pick a tool from the request examples below. The tool’s payload comes back as a JSON-encoded string in result.content[0].text. Every call is scoped to the API key’s user — no tool takes an identity argument. Batch (array) bodies are rejected. getUserCards with includeCardSecrets reveals a card’s PAN/CVV encrypted (the server never decrypts) and needs a sessionId built from getCardRevealPublicKey.
Authorizations
API token issued by your LootRush account manager. Sent as Authorization: Bearer <token>.