1Money Network MCP
OfficialRelated Servers
Alternatives to 1Money Network MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for the Monad blockchain. Provides tools for balances, transfers, swaps, and DeFi with Privy wallet signing.28 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server for interacting with the Solana blockchain. Provides tools to query balances, transactions, tokens, and network stats.15 npm1MIT
- FlicenseAqualityDmaintenanceA comprehensive MCP server for MetaApp development, offering tools for project initialization, protocol exploration, and blockchain interaction.15-
- AlicenseNot gradedqualityFmaintenanceA lightweight, fast MCP server that provides onchain capabilities for the LLMs and Agents.32 npm253MIT
- FlicenseNot gradedqualityDmaintenanceA comprehensive Bitcoin Cash (BCH) MCP server that enables wallet management, transaction utilities, and full CashToken operations including genesis, minting, and burning. It also provides advanced features such as escrow contracts, smart contract documentation, and real-time currency conversion.-
- AlicenseAqualityCmaintenanceMCP server for local transaction signing across EVM, UTXO, Tron, and XRP blockchains, with no network calls or API keys required.6137 npmMIT
TDQS
Scored across 32 tools
Tools are mostly distinct by domain area (accounts, chain, checkpoints, tokens, transactions, utils). A few pairs like tokens_issue vs tokens_mint or accounts_get_nonce vs accounts_get_bbnonce could be ambiguous without descriptions, but the verb/object division generally clarifies purpose.
All tool names follow a consistent group_verb_object pattern with snake_case throughout (e.g., accounts_get_nonce, tokens_burn, transactions_estimate_fee). Even compound actions like bridges_and_mints maintain the same style, so the naming is highly predictable.
With 32 tools, the server feels overloaded. Many utilities (utils_typeof, utils_safe_promise_all, utils_safe_promise_line) are not domain-specific and could be omitted, while the core token and transaction areas are well-covered. The count exceeds a comfortable scope for an MCP server.
The tool surface covers core blockchain operations: account nonces, chain ID, checkpoint queries, token lifecycle (issue, mint, burn, pause, whitelist/blacklist, metadata, authority), and transaction submission/estimation/retrieval. Minor gaps exist, such as an explicit token transfer tool (though payment may cover that) and no direct block query, but overall coverage is strong.