Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoPort for the CryptoMCP gateway and Anti-Drainer Control Dashboard.8090
ADMIN_PASSWORDYesDashboard admin password credential.
ADMIN_USERNAMEYesDashboard admin username credential.
MAX_DAILY_TX_USDNoMaximum allowed cumulative daily transaction value in USD.500
MAX_SINGLE_TX_USDNoMaximum allowed value for a single transaction in USD.100
BLOCK_INFINITE_ALLOWANCENoWhether to block transactions attempting infinite or unbounded token allowances.true
HUMAN_APPROVAL_THRESHOLD_USDNoUSD threshold at or above which a human-in-the-loop cryptographic approval token is required.25

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
completions
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_walletsA

List managed public wallet addresses and real-time balances across chains.

list_whitelisted_contractsB

List pre-approved decentralized protocols, routers, and recipient addresses.

transfer_cryptoA

Initiate a crypto transfer or contract interaction. Gated by Anti-Drainer guards, zero-infinite-allowance, and human challenge tokens.

submit_crypto_approval_tokenA

Submit an approval challenge token granted by the human supervisor to finalize and broadcast a high-value on-chain transaction.

get_crypto_security_statusA

Inspect active Anti-Drainer guards, single/daily spending caps, and emergency lockdown status.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 5 tools

Disambiguation4/5

The tools mostly have distinct purposes: listing wallets, listing whitelisted contracts, transferring, submitting an approval token, and checking security status. However, transfer_crypto and submit_crypto_approval_token are adjacent in the transaction workflow and could be confused by an agent unfamiliar with the approval gating.

Naming Consistency5/5

All tools use snake_case with a predictable verb_noun pattern (list_, transfer_, submit_, get_). The extra 'crypto' qualifier in some names is consistent with the server's domain and does not break the pattern.

Tool Count5/5

Five tools is well-scoped for a crypto transaction and security server. Each tool earns its place by covering a distinct part of the workflow without excessive surface area.

Completeness3/5

The surface covers listing wallets, listing whitelisted contracts, initiating transfers, submitting approval tokens, and inspecting security status. However, notable gaps remain: there is no transaction status/history lookup, no approval revocation, no wallet creation/import, and security status is read-only with no tool to trigger or clear lockdown.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues