Monei MCP Server
Related Servers
Alternatives to Monei MCP Server
No user-submitted related servers found.
Related Servers
FlicenseBqualityBmaintenanceMCP server that exposes Moolre's API as 24 tools for AI agents, enabling account management, transfers, payments, SMS, and WhatsApp operations.24-- AlicenseBqualityDmaintenanceAn MCP server to provide AI agents money functionalities via Nostr and Cashu.670 npm17MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that lets any AI agent operate a wallet directly on-chain: create wallets, send, swap, bridge, and deploy contracts across EVM and Bitcoin networks.1MIT

@gravv/mcpofficial
AlicenseAqualityAmaintenanceMCP server for the Gravv payments API that lets AI assistants onboard customers, run KYC, open accounts, move money, issue cards, and exchange currency, with built-in documentation search and safety confirmations for money-moving operations.27 npmMIT- AlicenseNot gradedqualityCmaintenanceAn MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.415 npm1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Starling Bank API integration, enabling AI agents to manage accounts, view transactions, and send payments via natural language.155 npm5MIT
TDQS
Scored across 24 tools
Each tool maps to a distinct resource/action pair—wallet balances, EVM/Solana portfolios, sends, swaps, offramp, bank lookups, and bill payments. Status-checking tools are clearly separated by domain (deposit link, offramp, transaction, bill history), and descriptions explicitly point to the right tool for each scenario. No two tools appear interchangeable.
All tools share the consistent monei_ prefix and follow a predictable snake_case verb_noun pattern (get_, send_, swap_, pay_, verify_). Minor verb variation like check_deposit_status versus track_offramp is semantically appropriate and does not break the naming convention.
24 tools is at the upper end of the 16–25 heavy band, which feels like a lot for a single MCP server. The broad fintech scope—NGN wallet, EVM and Solana crypto operations, offramp, and bill payments—justifies much of the surface, but splitting into wallet/crypto/bills sub-servers would improve focus.
Core lifecycles are well covered: deposits generate and check, sends cover bank/user and EVM/Solana, offramp has quote/execute/track, and bills have providers/pay/history. However, monei_pay_bill instructs agents to call monei_validate_bill before data and cable payments, but that tool is not exposed in the server—a concrete dead-end in the bill-payment flow. A swap quote/preview tool is also absent, though slippage defaults soften that gap.