Nagora MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NAGORA_API_KEY | No | Optional. Overrides the stored credential from register_agent. | |
| NAGORA_API_URL | No | Point at http://localhost:5004 for local dev. | https://api.nagora.shop |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Full-text search over active listings on nagora.shop. No API key required. Prices are in the listing's display currency with a Nano (XNO) equivalent. Returns an items array and total count. Use get_listing for full detail before purchasing. |
| get_listingA | Fetch a single listing by ID. No API key required. Returns full detail including variants, delivery options, and pricing. Use the returned Nano total as quotedTotalNano when purchasing to guard against exchange-rate drift. |
| register_agentA | Creates a Nagora agent and mints its API key in one call. No Nagora account or signup required. The key is saved to ~/.nagora/credentials.json and used automatically by all other tools from now on. Requires a name and a nano_ address (your wallet; refunds are routed there if an order is cancelled). Self-registered keys carry conservative default spending caps, returned in the result. Skip this tool if a key is already configured; check with whoami. |
| whoamiA | Verifies the configured API key and returns the agent's identity, per-transaction and per-day spending caps, callback URL, and webhook secret. Call this first to confirm the key works. |
| create_purchaseA | Places an order against a listing. Returns a depositAddress (per-order escrow Nano account) and amountNano. IMPORTANT: the order is not funded by this call. Send exactly amountNano to depositAddress from the agent's Nano wallet to fund escrow. Once funds are detected the order moves to AwaitingShipment automatically. Funds are held in escrow until confirm_delivery, so the buyer is protected if the item never arrives. Physical listings require a shippingAddress. |
| get_orderA | Polls an order placed by this agent. Returns orderStatus, escrowStatus, funding timestamps, tracking info, and the receipt ID once available. Poll after funding the deposit address, and after the seller ships, before calling confirm_delivery. |
| confirm_deliveryA | Confirms the goods or digital content arrived and releases the escrowed funds to the seller. Requires the order's escrowStatus to be Shipped. Call promptly once delivery is verified: the seller is waiting on this to get paid. If never called, an auto-finalise timer releases funds after the configured window. |
| cancel_orderA | Cancels an order whose escrow is still Initiated (no on-chain funds sent yet). Restores listing stock. Cannot cancel once escrow is Funded; use the dispute or refund flow on the website instead. |
| get_receiptA | Returns the cryptographically signed receipt for a completed order, including the seller's Nano address, the on-chain payout block hash, and Nagora's KMS signature. Available only after escrow is Released; returns an error while the order is still in progress. |
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 9 tools
Each tool has a clearly distinct purpose: listing search/detail, agent registration/auth, purchase creation, order status, cancellation, delivery confirmation, and receipt retrieval are all well-separated. There is little risk of selecting the wrong tool for a given action.
Most tools follow a consistent verb_noun snake_case pattern such as get_order, cancel_order, search_listings, and create_purchase. The only outlier is whoami, which is a familiar standalone command but does break the pattern slightly.
Nine tools is well-scoped for a marketplace agent server. Each tool covers a necessary part of the buyer/escrow workflow and none feel redundant or extraneous.
The set covers the full purchasing lifecycle: register, authenticate, search, view listing, place order, poll status, cancel, confirm delivery, and retrieve receipt. Minor gaps exist such as no list_orders or in-MCP dispute/refund handling, but those are partially external or non-essential for the core flow.