Model Context Protocol high risk

Token Minter

This MCP server provides AI agents with the ability to deploy, manage, and transfer ERC-20 tokens across 21 blockchains, leveraging Infura and a private key.

Connections & Capabilities

Connects To

GitHub

Capabilities

writeexecread

Quickstart

Install

npx hardhat

Config

{
  "mcpServers": {
    "Token-Minter-MCP": {
      "command": "node",
      "args": ["path/to/token-minter-mcp/server/index.js"],
      "env": {
        "INFURA_KEY": "your infura key",
        "PRIVATE_KEY": "your private key"
      }
    }
  }
}

Exposed MCP Tools (6)

critical

deployToken

Deploys a new ERC-20 token with specified parameters on a given blockchain.

Deploys a smart contract, which can have unintended consequences if the contract has vulnerabilities or is configured incorrectly.

high

transferToken

Transfers ERC-20 tokens from the current account to a specified address on a given blockchain.

Initiates token transfers, potentially leading to financial loss if the recipient address or amount is incorrect.

safe

getTransactionInfo

Retrieves transaction details for a given transaction hash on a specified blockchain.

Read-only operation that retrieves information about a transaction.

safe

getTokenBalance

Queries the balance of a specific ERC-20 token for the current account on a given blockchain.

Read-only operation that retrieves the balance of a token.

safe

getTokenInfo

Queries ERC-20 token metadata (name, symbol, decimals, total supply) for a given token address on a specified blockchain.

Read-only operation that retrieves token metadata.

safe

getBalance

Checks the native token balance of the current account on a specified blockchain.

Read-only operation that retrieves the native token balance.

Safety Assessment

This MCP server is risky due to its ability to deploy and transfer tokens, coupled with the need to expose a private key. It is safe to use only if the private key is securely managed and the user fully understands the implications of each transaction. Misuse or compromise could lead to financial loss.

Requires a private key for signing transactions, limiting unauthorized access if the key is secured.
Uses Infura for EVM network access, abstracting away the need to manage blockchain nodes directly.
Provides tools for querying token metadata, which are read-only operations.
Offers a 'deployTokenGuide' prompt to assist users in deploying tokens correctly.

Exposes private key via environment variable, posing a significant risk if compromised.
Allows token deployment and transfers, potentially leading to unintended financial consequences.
Lacks built-in rate limiting or access controls, increasing the risk of abuse.
Transaction execution relies on external services (Infura), introducing dependency risks.
No sandboxing or rollback mechanisms are mentioned, increasing the impact of errors.