Naira Offramp MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OFFRAMP_MODE | Yes | Set to `demo` when registering the MCP server, e.g. `--env OFFRAMP_MODE=demo`. The current release is a simulated demo; live mode is unavailable. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_balanceA | Inspect the USDC balance for Arc cashouts. Demo values are simulated; this does not move funds. |
| get_default_bankA | Get the saved recipient's bank, name, and masked account ending. No bank is chosen automatically. |
| set_default_bankA | Verify and save a default Nigerian bank account once. Requires human approval through the MCP client. Demo accepts only Demo Bank / 0000000000 / DEMO USER. |
| prepare_payoutA | Prepare a quote; no funds move. NGN means exact naira to receive; USDC means maximum total spend including all fees. Defaults to the saved bank. Supply a bank only when the user explicitly requests another destination. Repeated calls create separate quotes. |
| execute_payoutA | Request human approval for the exact prepared quote, then execute it at most once. Never claims bank credit from a chain receipt alone. Repeated calls inspect the existing payout; uncertain submissions require reconciliation and must not be resent. |
| payout_statusA | Inspect an existing payout. Reports completed only after the payout provider confirms completion. A demo completion is simulated and always has bankPaid=false. Never sends funds. |
| payout_historyA | List the ten most recent payouts in this local mode/profile. Bank account numbers are masked. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action in the payout lifecycle: reading balance, managing the saved bank, listing history, inspecting a single payout, and the prepare/execute two-phase flow. prepare_payout vs execute_payout and payout_history vs payout_status are clearly delineated by descriptions that emphasize quote-vs-move and list-vs-inspect.
All names use consistent snake_case, and the verb_noun pattern (get_balance, set_default_bank, prepare_payout, execute_payout) is clear. The two noun-only names (payout_history, payout_status) are a minor deviation but remain readable and unambiguous.
Seven tools is well-scoped for an offramp flow: balance, bank config, quote, execution, status, and history. Every tool maps to a needed step, with no redundant or filler operations.
The surface covers the full payout lifecycle from bank setup through quoting, execution, status, and history, including a safety-oriented reconciliation path. Minor gaps exist around cancellation/refund or explicit fee-preview, but core workflows are covered.