Skip to main content
Glama
kukapay

wallet-generator-mcp

by kukapay
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Wallet Generator MCP

An MCP server for batch-generating wallets compatible with Ethereum and all EVM-compatible chains.

Features

  • Batch Wallet Generation: Generate 1 to 100 EVM-compatible wallets in a single request.

  • EVM Compatibility: Supports all EVM-compatible chains, including but not limited to Ethereum, Binance Smart Chain (BSC), Base, Polygon, Arbitrum, and Optimism.

Related MCP server: wallet-inspector-mcp

Prerequisites

  • Node.js: Version 18 or higher.

  • npm: For installing dependencies.

Installation

  1. Clone the repository:

    git clone https://github.com/kukapay/wallet-generator-mcp.git
cd wallet-generator-mcp

  2. Install dependencies:

    npm install

Usage

The generateWallets tool allows you to generate multiple EVM-compatible wallets, each including an address, private key, and mnemonic phrase. It accepts the following parameter:

  • count: The number of wallets to generate (integer, 1 to 100, default is 1).

The generated wallets are compatible with any EVM-based chain, such as Ethereum, Binance Smart Chain, Base, Polygon, Arbitrum, Optimism, and more.

Example

You can interact with the server using an MCP-compatible client. Below is an example of a natural language prompt to generate wallets:

Prompt: 

Generate 2 wallets for use on EVM-compatible chains like Ethereum or Binance Smart Chain.

Response: 

Here are your 2 generated wallets for EVM-compatible chains:  
1. Address: 0x1234...abcd, Private Key: 0x5678...efgh, Mnemonic: word1 word2 word3 ...  
2. Address: 0x9abc...def0, Private Key: 0x1a2b...3c4d, Mnemonic: word4 word5 word6 ...

License

This project is licensed under the MIT License. See the LICENSE file for details.

Available Tools

1 tool
generateWalletsB

Batch-generating ethereum wallets

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It implies a write operation ('generating') but doesn't disclose behavioral traits like security implications (e.g., private key handling), rate limits, or output format. The description adds minimal value beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient phrase ('Batch-generating ethereum wallets') with zero wasted words, clearly front-loading the core action. It's appropriately sized for a no-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of generating cryptographic wallets (a sensitive operation), the description is incomplete. No annotations or output schema exist to clarify safety, return values, or error handling, leaving significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0 parameters and 100% schema description coverage, the schema fully documents the lack of inputs. The description doesn't need to add parameter details, so it meets the baseline for this scenario.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Batch-generating ethereum wallets' clearly states the verb ('generating') and resource ('ethereum wallets'), with 'batch-' indicating multiple outputs. However, it lacks sibling tools for differentiation, preventing a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool, such as for testing, bulk account creation, or specific blockchain contexts. The absence of sibling tools means no alternative comparisons are needed, but basic usage context is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedgenerateWallets
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as batch-generating Ethereum wallets, making it straightforward for an agent to select.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'generateWallets' follows a clear verb_noun pattern, and there are no other tools to cause inconsistency.

Tool Count2/5

A single tool for a wallet generator server is too few for typical scope, as it lacks operations like listing, deleting, or managing wallets. This minimal set limits functionality and may cause agent failures in broader workflows.

Completeness2/5

The server is severely incomplete for a wallet management domain. It only supports generation, with no tools for reading, updating, deleting, or other essential operations like signing transactions, making it inadequate for comprehensive agent use.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kukapay/wallet-generator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server