Skip to main content
Glama
Rift Finance MCP Server

Rift Finance MCP Server

Official
by Rift-FI

rift_offramp

Withdraw USDC or USDT to local fiat via mobile money or bank by generating a passkey approval link, then track the payout status.

Instructions

Withdraw crypto to fiat. REAL PAYMENT — confirm with user. Requires: login + merchant approval + KYC (>$20) + a passkey.

Does NOT execute directly: returns an APPROVAL REQUIRED link. Give it to the user to approve with their passkey; check with rift_get_approval, then track the payout with rift_poll_offramp_status. Never call again to retry. No OTP/password needed.

WARNING: after approval, settlement can take 30-60+ seconds (on-chain tx + fiat settlement). A timeout does NOT mean failure — always check rift_poll_offramp_status with the transactionCode to confirm the actual status.

The 'recipient' field is a JSON string whose structure depends on the currency:

KES (Kenya Mobile — Pretium): {"type":"MOBILE","accountIdentifier":"+254...","institution":"Safaricom"} — accountName is NOT required for KES/M-Pesa KES (Kenya Paybill): {"type":"PAYBILL","accountIdentifier":"shortcode","accountNumber":"acct_num","institution":"Safaricom"} NGN (Nigeria Bank — Paycrest): {"bankCode":"GTBINGLA","accountIdentifier":"0123456789","accountName":"John Doe","institution":"GTBank"} UGX (Uganda Mobile): {"bankCode":"MOMOUGPC","accountIdentifier":"+256...","accountName":"Name","institution":"MTN"} GHS (Ghana Mobile): {"bankCode":"MOMOGHPC","accountIdentifier":"+233...","accountName":"Name","institution":"MTN"} ETB (Ethiopia Mobile): {"bankCode":"TELEBPC","accountIdentifier":"+251...","accountName":"Name","institution":"Telebirr"} CDF (Congo Mobile): {"bankCode":"OMONDFPC","accountIdentifier":"+243...","accountName":"Name","institution":"Orange Money"} TZS (Tanzania Mobile): {"bankCode":"TIGOTZPC","accountIdentifier":"+255...","accountName":"Name","institution":"Vodacom"} MWK (Malawi Mobile): {"bankCode":"AIRTMWPC","accountIdentifier":"+265...","accountName":"Name","institution":"Airtel"} BRL (Brazil PIX): {"bankCode":"PIXKBRPC","accountIdentifier":"pix_key","accountName":"Name","institution":"pix"}

Call rift_get_payment_methods first to get valid bankCode and institution values for the user's currency. Use amount (USDC) or localAmount (exact fiat payout). Use rift_preview_exchange_rate with type='offramp' to show rates/fees first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>",
      "currency": "<currency>",
      "chain": "<chain>",
      "recipient": "<recipient>"
    },
    "name": "rift_offramp"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYesREQUIRED. Source chain: BASE, ARBITRUM, POLYGON, ETHEREUM, CELO
tokenYesREQUIRED. Token to sell: USDC or USDT
amountNoAmount in USDC to sell. Provide this OR localAmount, not both
currencyYesREQUIRED. Fiat currency: KES, NGN, UGX, GHS, ETB, CDF, TZS, MWK, BRL
recipientYesREQUIRED. JSON string — structure depends on currency. See tool description for formats. Call rift_get_payment_methods to find valid bankCode/institution values
localAmountNoExact fiat amount user wants to RECEIVE. Provide this OR amount, not both

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden and does so: it discloses the real-money nature, required auth (login + merchant approval + KYC >$20 + passkey), that no OTP/password is needed, that no funds move until user approval, and that settlement takes 30-60+ seconds with timeouts not implying failure. This is exactly the operational context an agent needs before invoking a destructive financial operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the warning and workflow before the schema enumeration, and every section earns its place. The ten currency templates make it long, but they are load-bearing reference data rather than padding, so the length is justified even though it could arguably be compressed into a table or deferred to rift_get_payment_methods output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, high-stakes financial tool with no annotations and no output schema, the description covers prerequisites, invocation semantics, non-execution behavior, failure interpretation, and the trickiest parameter's format. Nothing an agent must know to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, but the description adds substantial meaning beyond it by enumerating the currency-specific JSON structure of the 'recipient' string (KES Pretium vs Paybill, NGN Paycrest, and eight mobile-money variants), noting which fields are unnecessary for KES/M-Pesa, and clarifying the amount (USDC) vs localAmount (exact fiat received) tradeoff.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: 'Withdraw crypto to fiat,' and immediately marks it as a REAL PAYMENT. The follow-on workflow paragraph makes clear it does not settle directly but returns an APPROVAL REQUIRED link, distinguishing it from rift_get_offramp_orders and rift_offramp_create_order.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use and how to sequence: 'Call rift_get_payment_methods first,' use rift_preview_exchange_rate with type='offramp' to show rates first, then approve via rift_get_approval and track with rift_poll_offramp_status. It also gives a firm negative rule ('Never call again to retry') and the timeout caveat, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools