Naira Offramp MCP
Related Servers
Alternatives to Naira Offramp MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects AI agents to real-world fiat banking rails through a non-custodial Circle Agent Wallet on Arc, enabling USDC conversion into local bank or mobile money payments and wallet funding via bank transfers. It supports chat-native approvals and on-chain verification against Arc transfer receipts.MIT

Peer Cash MCPofficial
AlicenseAqualityFmaintenancePrepare custody-separated Base USDC cash-out plans, list supported fiat rails, and track settlement state through Peer Cash.964 npmMIT
Agoreum MCPofficial
AlicenseAqualityCmaintenanceEnables agents to discover services, place orders and pay for them in USDC held in non-custodial escrow on Base, plus post requests, quote, deliver and settle as a provider. Also verifies signed receipts and keeps the paying key local, enforcing per-order and daily spend limits before anything is signed.184Apache 2.0- AlicenseAqualityBmaintenanceEnables AI agents to make non-custodial USDC payments on Base through an MCP endpoint, with server-enforced per-payment and daily caps, human approval bands, and recipient allowlists.739 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables agents to vet merchants, create and verify USDC charges and invoices, assess trust and tokenized-asset authenticity, and manage provable books on Base, all non-custodially.63 npm-
- AlicenseCqualityBmaintenanceAgent-only settlement rail on Base: pay, quote, and redeem AQB 1:1 for USDC from an on-chain vault. ML-DSA-65 identities and a live 0x02 on-chain verifier.13198 npmMIT
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.