Armor Crypto MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARMOR_API_KEY | Yes | Your Armor API key (required - you need to have the Armor NFT to get an API Key) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_armor_mcp_versionB | Get the current Armor Wallet version |
| wait_a_momentB | Wait for some short amount of time, no more than 10 seconds |
| get_current_timeB | Gets the current time and date |
| calculatorA | |
| get_wallet_token_balanceC | |
| calculate_token_conversionC | |
| swap_quoteC | |
| swap_transactionC | |
| get_all_walletsC | |
| get_all_ordersC | |
| search_official_token_addressA | |
| search_token_detailsB | |
| list_groupsB | |
| list_single_groupC | |
| create_walletC | |
| archive_walletsC | |
| unarchive_walletsC | |
| create_groupsC | |
| add_wallets_to_groupB | |
| archive_wallet_groupC | |
| unarchive_wallet_groupC | |
| remove_wallets_from_groupC | |
| transfer_tokensC | |
| create_dca_orderC | |
| list_dca_ordersC | |
| cancel_dca_orderD | |
| create_orderC | |
| cancel_orderC | |
| stake_quoteC | |
| unstake_quoteC | Retrieve an unstake quote. Expects a UnstakeQuoteRequestContainer, returns a SwapQuoteRequestContainer. |
| stake_transactionD | |
| unstake_transactionC | |
| get_top_trending_tokensC | |
| get_stake_balancesB | |
| rename_walletsD | |
| get_token_candle_dataC | Get candle data about any token for analysis. Expects a CandleStickRequest, returns a list of candle sticks. |
| send_key_to_telegramD | Send the mnemonic or private key to telegram. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| login_prompt | A sample prompt to ask the user for their access token after providing an email. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 37 tools
The tools cover distinct areas like wallets, groups, orders, swaps, and staking, but there is some overlap. For example, 'search_official_token_address' and 'search_token_details' both search for token information, and 'cancel_dca_order' and 'cancel_order' both cancel orders, which could cause confusion. However, the descriptions help clarify their specific purposes.
Most tools follow a consistent verb_noun pattern (e.g., 'create_wallet', 'list_groups', 'archive_wallets'), but there are minor deviations like 'calculator' (noun only) and 'wait_a_moment' (verb phrase). Overall, the naming is predictable and readable, with only a few inconsistencies.
With 37 tools, the count is excessive for a crypto wallet server, making it heavy and potentially overwhelming. While the domain is broad, many tools could be consolidated (e.g., multiple archive/unarchive tools) or omitted (e.g., 'get_current_time', 'wait_a_moment'), leading to a bloated interface.
The tool set provides comprehensive coverage for crypto wallet management, including CRUD operations for wallets and groups, trading (orders, swaps), staking, and token analysis. Minor gaps exist, such as no direct tool for editing wallet details beyond renaming, but agents can work around this with existing tools.