Peppermint MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PEPPERMINT_API_KEY | Yes | Your Peppermint API key | |
| PEPPERMINT_INSECURE_KEY | No | Set to '1' for Plain API Key authentication, '0' for HMAC-SHA512 | 1 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_auth_infoB | Get information about current authentication method |
| list_blockchainsB | List all available blockchains |
| get_blockchainA | Get details of a specific blockchain |
| list_contractsB | List all contracts |
| get_contractB | Get details of a specific contract |
| deploy_contractC | Deploy a new smart contract |
| read_contractC | Read data from a smart contract |
| write_contractC | Write data to a smart contract |
| list_transactionsB | List all transactions |
| get_transactionB | Get details of a specific transaction |
| list_vaultsB | List all vaults |
| get_vaultB | Get details of a specific vault |
| create_vaultC | Create a new vault |
| create_walletC | Create a new wallet |
| create_tokenB | Create a new ERC20 token |
| mint_tokenC | Mint tokens to an address |
| burn_tokenC | Burn tokens from the caller |
| transfer_erc20B | Transfer ERC20 tokens from a wallet to another address |
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 18 tools
Most tools have clear, distinct purposes (auth, blockchains, contracts, transactions, vaults, tokens). A few near-boundaries exist, e.g., create_token vs deploy_contract, but descriptions clarify the difference.
All tool names follow a consistent verb_noun snake_case pattern (get_, list_, create_, deploy_, read_, write_, mint_, burn_, transfer_). No mixed conventions or vague names.
18 tools is on the higher side but appropriate given the broad scope covering blockchains, contracts, transactions, vaults, and tokens. Each tool addresses a distinct operation, though a few could be consolidated without loss.
The surface covers core operations for auth, blockchain info, contract lifecycle (deploy/read/write), transactions, vaults, and token management. Missing native token transfers or wallet balance queries are minor gaps given the token/contract focus.