bsc-multisend-mcp

Related Servers

Alternatives to bsc-multisend-mcp

No user-submitted related servers found.

Related Servers

bnbchain-mcpofficial
Blockchain Web3 & Decentralized Tech Code Execution
bnb-chain
A
license
B
quality
B
maintenance
A MCP server for BNB Chain that supports BSC, opBNB, Greenfield, and other popular EVM-compatible networks.
Updated 5 months ago (2026-04-17 01:56 UTC)
26
90 npm
60
MIT
BSC MCP Server
Blockchain Web3 & Decentralized Tech Code Execution
TermiX-official
A
license
C
quality
F
maintenance
A 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.
Updated a year ago (2025-08-30 03:22 UTC)
12
10 npm
105
MIT
BNB Chain MCP
Blockchain Web3 & Decentralized Tech Finance
nirholas
A
license
Not graded
quality
B
maintenance
A 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.
Updated 9 days ago (2026-09-15 08:00 UTC)
22 npm
33
-
Stargate Bridge MCP
Blockchain Cryptocurrency Web3 & Decentralized Tech
kukapay
A
license
A
quality
D
maintenance
An MCP server that enables cross-chain token transfers via the Stargate protocol.
Updated a year ago (2025-10-27 12:19 UTC)
4
1
MIT
wallet-generator-mcp
Blockchain Web3 & Decentralized Tech
kukapay
A
license
B
quality
D
maintenance
An MCP server for batch-generating wallets compatible with Ethereum and all EVM-compatible chains.
Updated a year ago (2025-07-02 01:45 UTC)
1
1
MIT
honeypot-detector-mcp
Blockchain Security Web3 & Decentralized Tech
kukapay
A
license
A
quality
D
maintenance
An MCP server that detects potential honeypot tokens on Ethereum, BNB Smart Chain (BSC), and Base.
Updated a year ago (2025-06-14 13:34 UTC)
1
3
MIT

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

B3.3/5.0

Scored 2026-04-18 09:41 across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness2/5

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.