Nano Currency MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NANO_RPC_URL | Yes | URL which should be used to communicate with a Nano node RPC. This can be a local or remotely hosted endpoint. | |
| NANO_PRIVATE_KEY | Yes | Nano private key which will be used to sign send transactions and to derive the Nano address from. Used by tools nano_send and nano_my_account_info | |
| NANO_MAX_SEND_AMOUNT | No | Maximum amount (in nano/Ӿ units) which can be sent in a single transaction. For safety purposes the default maximum send amount is 0.01 nano (Ӿ0.01). | 0.01 |
| NANO_WORK_GENERATION_URL | No | URL which should be used to communicate with an endpoint that supports the work_generate RPC command for work generation. If not specified, defaults to NANO_RPC_URL. Used by tool nano_send |
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 |
|---|---|
| nano_sendC | Send a specified amount of Nano currency from a predefined account to a destination Nano address. |
| nano_account_infoA | Retrieve detailed information about a specific Nano account/address, including balance (in Nano and raw units), representative, and frontier block. |
| nano_my_account_infoA | Retrieve detailed information about my Nano account/address, including balance (in Nano and raw units), representative, and frontier block. This is the account that is used to send Nano from. |
| block_infoB | Retrieve detailed information about a specific Nano block. |
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 4 tools
There is significant overlap between 'nano_account_info' and 'nano_my_account_info', as both retrieve account information with only the source differing (specific vs. predefined). This ambiguity could lead to misselection, especially since 'nano_my_account_info' is essentially a subset of 'nano_account_info' with a fixed account. The other tools are distinct, but this core overlap reduces clarity.
The naming follows a consistent snake_case pattern with 'nano_' prefix for most tools, making them readable and predictable. However, 'block_info' deviates by lacking the 'nano_' prefix, which slightly breaks the convention. Overall, the naming is mostly consistent with only minor deviations.
With 4 tools, the count is borderline thin for a currency server, as it covers only basic retrieval and sending. While it includes essential operations, it feels slightly under-scoped for a full Nano currency interface, lacking tools for transactions like receiving, history, or network status, which might be expected in this domain.
The tool set has significant gaps for a Nano currency server. It includes account info retrieval and sending, but misses critical operations such as receiving transactions, checking transaction history, monitoring network status, or managing multiple accounts. This incompleteness could cause agent failures when trying to perform common currency-related tasks beyond basic queries and transfers.