Skip to main content
Glama
Adeyemir

Naira Offramp MCP

by Adeyemir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Naira Offramp MCP

No user-submitted related servers found.

    Related Servers

    • veyra-mcp

      zapxlabs
      A
      license
      A
      quality
      B
      maintenance
      Enables 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.
      7
      44 npm
      MIT

    • AbaPay

      investorphem
      A
      license
      A
      quality
      B
      maintenance
      Non-custodial stablecoin bill payments (airtime, data, electricity, cable, education) on Celo mainnet, reachable via x402 (zero setup, EIP-3009), a linked wallet's PIN-gated MCP/A2A tool catalog, or plain natural language on Telegram/WhatsApp/X.
      10
      1
      MIT

    • Rill MCP

      rillongit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to accept and spend payments via Rill's network, including pay links, wallets, and Connect onboarding.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources