base-batch-send-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEPLOYER_PRIVATE_KEY | Yes | Private key for sending transactions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| batch_send_ethA | Send ETH to multiple recipients in a single transaction on Base. Requires DEPLOYER_PRIVATE_KEY env var. A small batch fee (0.0005 ETH) is charged per batch. |
| batch_send_erc20A | Send ERC-20 tokens to multiple recipients in a single transaction on Base. Automatically handles token approval. Requires DEPLOYER_PRIVATE_KEY. Batch fee: 0.0005 ETH. |
| estimate_batchA | Estimate gas cost and total ETH needed for a batch send operation. Use before executing to verify costs. |
| get_batch_infoA | Get BatchSender contract info — current fee, treasury address, contract address. Use to verify the contract is live and check fees before sending. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: sending ERC-20, sending ETH, estimating costs, and retrieving contract info. No overlap in functionality.
All tools follow a consistent verb_noun snake_case pattern (batch_send_*, estimate_batch, get_batch_info), making them predictable.
Four tools is well-scoped for a focused batch-sending server. Each tool serves a necessary role without redundancy or gaps.
The set covers the full workflow: estimation before sending, both token and ETH transfers, and contract info retrieval. No obvious missing operations for the stated purpose.