raw_sendLABSCO SUMMARY
The default cap is the design, not an afterthought.
A server that spends money on a model's say-so needs a limit that does not depend on the model behaving, and this one ships with a small ceiling that you must raise by hand before larger sends are possible. The author's own advice is to test with an account holding a small balance. The x402 tool is the forward-looking piece: it produces the header an agent needs to pay for an API call rather than only sending to a person.
What it is
An MCP server that lets a client move real cryptocurrency. It signs and sends Nano from an account derived from a private key you supply, reads account and block state from a Nano node's RPC, and can build the payment signature header for an x402 transaction so an agent can pay for an API or resource. The maximum send per transaction is capped in configuration, and the default cap is deliberately small.
What you get
- Nano sent to a destination account, in either unit —
nano_sendfor nano units,raw_sendfor raw - An account's balance in both nano and raw, with its representative and frontier block — for any account, or for the sending account specifically —
nano_account_info,nano_my_account_info - A specific block's detail read back —
block_info - The
PAYMENT-SIGNATUREheader for a Nano x402 transaction under the exact scheme, which is how an agent pays for a resource programmatically —x402_payment_signature_exact_scheme_create - A hard per-transaction ceiling: the default maximum is 0.01 nano, and sending more requires you to set
NANO_MAX_SEND_AMOUNTorRAW_MAX_SEND_AMOUNTexplicitly
Requirements
Node.js with NPM, then clone and npm install. NANO_RPC_URL is required — a local or remote Nano node RPC endpoint. NANO_PRIVATE_KEY is the account's private key, and the README is emphatic that this is the private key and not the wallet seed; the sending account is derived from it. NANO_WORK_GENERATION_URL defaults to the RPC URL if unset. X402_NANO_NETWORK defaults to nano:mainnet. The send caps default to 0.01 nano and must be raised deliberately.
Setup effort
Build from source — clone the repository, then follow the project's own run instructions
USE CASES
01
Making a payment from a conversation
Send to the destination account in nano units, within the ceiling you configured — the cap applies whatever the model asks for.
02
Checking the balance before and after
Read the sending account's own information, including its frontier block, rather than trusting the send tool's return alone.
03
Letting an agent pay for an API call
Create the x402 payment signature header under the exact scheme and attach it to the request.
04
Investigating a transaction that looks wrong
Read the block detail directly rather than reading a block explorer's rendering of it.
6 tools
Listed in project docs. Your client may show a different list.
nano_sendnano_account_infonano_my_account_infoblock_infox402_payment_signature_exact_scheme_createBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
NANO_PRIVATE_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
ENTER FULL FILE PATH TO node.exe ON YOUR SYSTEM ENTER FULL FILE PATH TO nano-currency.js FILE FROM THIS REPOSITORYMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"nano_currency": {
"command": "ENTER FULL FILE PATH TO node.exe ON YOUR SYSTEM",
"args": [
"ENTER FULL FILE PATH TO nano-currency.js FILE FROM THIS REPOSITORY"
],
"env": {
"NANO_RPC_URL": "ENTER YOUR NANO_RPC_URL",
"NANO_PRIVATE_KEY": "ENTER YOUR NANO_PRIVATE_KEY"
}
}
}
}
