Nagora
REMOTE · API.NAGORA.SHOP · 2 COMPONENTS
Buy real goods with Nano (XNO) through escrow. Search, purchase, track orders, get signed receipts.
Available components
Last scanned (23 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1126 tokens (~125/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Oct 26 0
- Stability: 0.97 → pass security
- 10 Oct 26 0
- Tool “get_order” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.nagora.shop/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.nagora.shop | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 10 Feb 2026 | 11 Mar 2027 | RSA 2048 | SHA256-RSA | 9bd2abe0d1cce2081e3b04719b8d92f |
| SANs: api.nagora.shop | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.nagora.shop. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| shop. | DS published | 50701 | 8 | Verified |
| nagora.shop. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https: blob:; font-src 'self' data: https:; connect-src 'self' wss: https: ws:; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.nagora.shop/mcp | Verified | 200 | |
| http (plaintext) | http://api.nagora.shop/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_order ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string|null | – | Agent API key (nag_agt_...). Omit when connected with an Authorization header |
| orderId | string | yes | Order ID to cancel |
No output schema declared.
No examples provided.
confirm_delivery ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string|null | – | Agent API key (nag_agt_...). Omit when connected with an Authorization header |
| orderId | string | yes | Order ID to confirm |
No output schema declared.
No examples provided.
create_purchase ~226
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. Physical listings require a shippingAddress.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string|null | – | Agent API key (nag_agt_...). Omit when connected with an Authorization header |
| deliveryOptionId | integer|null | – | Delivery option ID from get_listing, when the listing offers several |
| listingId | string | yes | Listing to purchase |
| quantity | integer | – | Quantity, default 1 |
| quotedTotalNano | number|null | – | Total in XNO from a recent get_listing call. Rejected if more than 2% off the live rate; omit to skip the guard |
| shippingAddress | object|null | – | Required for physical delivery; omit for digital listings |
| variantId | string|null | – | Variant ID from get_listing, when the listing has variants |
No output schema declared.
No examples provided.
get_listing ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listingId | string | yes | Listing ID from search_listings |
No output schema declared.
No examples provided.
get_order ~111
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. For digital listings, digitalContent holds what was bought once the order is paid.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string|null | – | Agent API key (nag_agt_...). Omit when connected with an Authorization header |
| orderId | string | yes | Order ID returned by create_purchase |
No output schema declared.
No examples provided.
get_receipt ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string|null | – | Agent API key (nag_agt_...). Omit when connected with an Authorization header |
| orderId | string | yes | Order ID to fetch the receipt for |
No output schema declared.
No examples provided.
register_agent ~208
Creates a Nagora agent and mints its API key in one call. No Nagora account or signup required. IMPORTANT: this is a remote server with no local storage, so the key is returned ONCE in the result. Store it securely and pass it as the apiKey argument on subsequent calls in this session; for long-lived setups reconnect with an 'Authorization: Bearer <key>' header instead. Skip this tool if a credential is already configured; check with whoami.
| Name | Type | Req | Description |
|---|---|---|---|
| callbackUrl | string|null | – | Optional webhook URL; Nagora POSTs signed order state-change events to it |
| contactEmail | string|null | – | Optional contact email for order issues |
| homepageUrl | string|null | – | Optional homepage describing the agent |
| name | string | yes | Agent name, e.g. 'claude-shopper' (max 64 chars) |
| nanoAddress | string | yes | Nano (XNO) address refunds should be sent to: the wallet this agent pays from |
No output schema declared.
No examples provided.
search_listings ~155
Full-text search over active listings on nagora.shop. No API key required. Returns an items array and total count. Use get_listing for full detail before purchasing.
| Name | Type | Req | Description |
|---|---|---|---|
| categoryId | integer|null | – | Numeric category filter |
| count | integer|null | – | Page size 1-100, default 20 |
| maxPrice | number|null | – | Maximum price filter |
| minPrice | number|null | – | Minimum price filter |
| q | string|null | – | Free-text search query, e.g. 'mechanical keyboard' |
| sortBy | string|null | – | Sort order: newest, price_asc, or price_desc. Default newest |
| startIndex | integer|null | – | Pagination offset, default 0 |
No output schema declared.
No examples provided.
whoami ~65
Verifies the configured credential and returns the agent's identity, spending caps, callback URL, and webhook secret. Call this first to confirm the credential works.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string|null | – | Agent API key (nag_agt_...). Omit when connected with an Authorization header |
No output schema declared.
No examples provided.
How do I install the Nagora MCP server?
Nagora is a hosted endpoint at https://api.nagora.shop/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.nagora.shop
claude mcp add --transport http shop-nagora-nagora 'https://api.nagora.shop/mcp'
What is the Nagora MCP server?
Nagora is an MCP server listed in the public MCP registry as shop.nagora/nagora. Buy real goods with Nano (XNO) through escrow. Search, purchase, track orders, get signed receipts. This page covers its hosted endpoint (https://api.nagora.shop/mcp).
Is the Nagora MCP server safe to use?
Nagora scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Nagora MCP server expose?
Nagora exposes 9 tools: search_listings, register_agent, confirm_delivery, get_order, whoami, and 4 more. Their descriptions and schemas cost roughly 1,126 tokens of context every time the server is loaded.
Does the Nagora MCP server require authentication?
No. We connected to Nagora without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nagora MCP server still maintained?
Nagora is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Nagora MCP server?
VerifyMCP ran 11 checks on Nagora, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Nagora: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.