bsc-multisend-mcp
Related Servers
Alternatives to bsc-multisend-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityCmaintenanceA MCP server for BNB Chain that supports BSC, opBNB, Greenfield, and other popular EVM-compatible networks.26100 npm59MIT- AlicenseCqualityFmaintenanceA backend service for executing transactions on Binance Smart Chain, enabling secure transfers of BNB and BEP-20 tokens, smart contract interactions, and token creation through structured MCP integration.1235 npm105MIT
- AlicenseNot gradedqualityBmaintenanceA comprehensive MCP server for interacting with the BNB Chain ecosystem, including BSC EVM operations, BNB Greenfield decentralized storage, and the Sperax Protocol. It enables users to manage wallets, execute token transactions, and handle storage buckets using natural language.64 npm34-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to launch and trade BSC tokens through an MCP server, with local wallet signing, dry-run mode, and configurable spending limits.295 npmMIT
- AlicenseAqualityDmaintenanceAn MCP server that enables cross-chain token transfers via the Stargate protocol.41MIT
- AlicenseBqualityDmaintenanceAn MCP server for batch-generating wallets compatible with Ethereum and all EVM-compatible chains.11MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one handles native BNB transfers and the other handles ERC20 token transfers. There is no overlap or ambiguity between them, as each targets a specific asset type with no functional duplication.
Both tools follow a consistent verb_noun pattern with 'distribute' as the verb and descriptive nouns ('Native', 'Token'). The naming is perfectly uniform and predictable across the set.
With only 2 tools, the set feels thin for a multisend server, lacking operations like checking balances, viewing transaction history, or handling batch configurations. While the core functionality is present, the scope is minimal and may limit agent workflows.
The server covers the basic distribution actions for two asset types but has significant gaps: no tools for querying contract status, validating addresses, estimating gas, or managing batches. This incomplete surface could lead to agent failures in complex scenarios.