Nafafy Storefront
REMOTE · NAFAFY.COM
Search the public Nafafy catalog and create firm checkout quotes.
Available components
Last scanned (4 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 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 Security66
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 314 tokens (~78/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 66
First indexed and scored.
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 5 Nov 2026 · Probed https://nafafy.com/api/mcp/storefront
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nafafy.com | CN=YE2,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6a2f8a8515b386d3c502feac6bd32954989 |
| SANs: *.nafafy.com, nafafy.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of nafafy.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| nafafy.com. | present | 2371 | 13 | Verified |
| nafafy.com. | Verified address RRset verified with the apex keys |
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' https://checkout.razorpay.com https://sdk.cashfree.com https://mercury.phonepe.com https://www.youtube.com https://www.youtube-nocookie.com https://s.ytimg.com https://static.cloudflareinsights.com https://accounts.google.com/gsi/client https://challenges.cloudflare.com 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://accounts.google.com/gsi/style; worker-src 'self' blob:; img-src 'self' data: blob: https:; media-src 'self' https: blob:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://nafafy.com wss://nafafy.com https: data: blob: https://api.razorpay.com https://api.cashfree.com https://sandbox.cashfree.com https://api.phonepe.com https://api-preprod.phonepe.com; frame-src 'self' https://accounts.google.com/gsi/ https://challenges.cloudflare.com https://api.razorpay.com https://checkout.razorpay.com https://sdk.cashfree.com https://mercury.phonepe.com https://www.google.com https://maps.google.com https:// |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=(self), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nafafy.com/api/mcp/storefront | Verified | 200 | |
| http (plaintext) | http://nafafy.com/api/mcp/storefront | HTTPS enforced | 301 | https://nafafy.com/api/mcp/storefront |
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 →
create_quote ~52
Create a firm 5-minute checkout quote for a set of items. Returns quote_id (pass it to /api/ucp/authorize with a signed agent mandate to complete checkout).
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
get_product ~31
Fetch one product by its Nafafy product id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Nafafy product id (uuid). |
No output schema declared.
No examples provided.
search_shop_catalog ~84
Search the public Nafafy catalog. Returns in-stock products with price, availability, URL, and merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category breadcrumb prefix. |
| limit | integer | – | Max results (default 20). |
| max_price_cents | integer | – | Optional max unit price in minor units. |
| query | string | – | Free-text search over product titles. |
No output schema declared.
No examples provided.
search_shop_knowledge ~102
Semantic + keyword search over Nafafy's commerce knowledge: a merchant's product details, policies and FAQs (when `host` is given) plus platform buying guides. Use this to answer questions like sizing, materials, returns, or shipping before recommending a product.
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | – | Optional merchant slug to include that store's docs. |
| k | integer | – | Max passages (default 6). |
| query | string | yes | The shopper's question. |
No output schema declared.
No examples provided.
How do I install the Nafafy Storefront MCP server?
Nafafy Storefront is a hosted endpoint at https://nafafy.com/api/mcp/storefront, 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 · nafafy.com
claude mcp add --transport http com-nafafy-storefront 'https://nafafy.com/api/mcp/storefront'
What is the Nafafy Storefront MCP server?
Nafafy Storefront is an MCP server listed in the public MCP registry as com.nafafy/storefront. Search the public Nafafy catalog and create firm checkout quotes. This page covers its hosted endpoint (https://nafafy.com/api/mcp/storefront).
Is the Nafafy Storefront MCP server safe to use?
Nafafy Storefront scores 67 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 Nafafy Storefront MCP server expose?
Nafafy Storefront exposes 4 tools: search_shop_catalog, get_product, create_quote, search_shop_knowledge. Their descriptions and schemas cost roughly 269 tokens of context every time the server is loaded.
Does the Nafafy Storefront MCP server require authentication?
No. We connected to Nafafy Storefront without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nafafy Storefront MCP server still maintained?
Nafafy Storefront is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.