nano-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NANO_PAYMENT_MASTER_SECRET | Yes | Master secret used to derive one-time payment addresses per request. |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_addressA | Return the one-time Nano payment address for request_id (or mint a fresh). |
| get_balanceA | Return the raw balance of a nano_ account via rpc.nano.to. |
| get_historyB | Return the last |
| quoteA | Price a call in Nano. Returns {request_id, address, price_raw, price_nano}
where |
| quote_usdA | Price a call in dollars. Converts the USD price to the exact XNO amount
via the MEDIAN of three independent public price sources and returns
{request_id, address, price_raw, price_usd, rate_xno_usd, expires_at}.
The quote expires in <=30s; pay the exact price_raw to |
| verify_paymentA | Service side: approve the call for request_id once an on-chain send of at least amount_raw is confirmed to its one-time address. Approves exactly once; a repeat returns status='spent'. |
| pay_and_callC | Agent side: given a quoted request_id, pay its one-time address and call
|
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 7 tools
Most tools target distinct actions: account queries (get_balance/get_history) are separate from the payment flow (quote/quote_usd/verify_payment/pay_and_call). get_address overlaps slightly with the one-time addresses returned by quote tools, and quote vs quote_usd are similar, but the descriptions clarify when each should be used.
The get_balance/get_history/get_address group follows a clear verb_noun pattern, and verify_payment is similarly structured. quote, quote_usd, and pay_and_call deviate a bit from that pattern but are still lowercase, readable, and verb-first.
Seven tools is well-scoped for a Nano payment/call gateway: account lookups, quoting, verification, and execution are covered without redundancy or bloat. Each tool has a clear place in the payment-and-call flow.
The core lifecycle is present: obtain an address, quote a price, pay, verify payment, and invoke the call, with balance/history utilities for account tracking. There is no explicit request-status or cancel/expiry operation, but agents can work around this via re-quoting or verify_payment's status return.