Nafafy Storefront
warningsnafafy.com
Search the public Nafafy catalog and create firm checkout quotes.
https://nafafy.com/api/mcp/storefrontWebsiteOAuthMCP 2026-07-28v1.0.0last checked 3 Nov 2026spoke MCP on 1 of 1 check (30 days)initialize in 495 msLast checked 3 Nov 2026
- ✓Answered the MCP handshake (MCP 2026-07-28)
- ✓Auth detected: OAuth
- ✓Lists 4 tools
- ✓No blockers or warnings
- ✓Spoke MCP on 1 of 1 check (30 days)
Will my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✕Claude CodeNot supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
Claude Code docs · read on 2026-08-30
✕Claude (claude.ai & Desktop)Not supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✕ChatGPTNot supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
ChatGPT docs · read on 2026-08-30
✕CursorNot supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
Cursor docs · read on 2026-08-30
✕VS Code (Copilot)Not supported
The authorization server advertises no S256 challenge method, which MCP's authorization spec requires — no compliant client has a method in common with it.
VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 3 Nov 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://nafafy.com |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✕None advertised MCP requires S256; a client that implements only that has no method in common with this server. |
| Grant types | urn:xavio:params:oauth:grant-type:ucp-signed-envelope |
| Scopes | ucp.catalog.read, ucp.checkout.write, ucp.mandates.write, ucp.leads.write |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 4 tools listable |
| Documentation | https://nafafy.com/auth.md |
What the probe found
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
The server exposes a public surface before authorization: search_shop_catalog, get_product, create_quote, search_shop_knowledge.
Neither the reserved <endpoint>/server-card location nor the domain's /.well-known/ai-catalog.json describes this endpoint (SEP-2127), so a client that discovers servers by domain will not find it.
Tools
Contract history
Watch this server
Save its public contract as a baseline and manage breaking-change email alerts.
Set up a watchRoute it through the gateway
Put this endpoint behind one find_tools / call_tool pair with the rest of your servers. Part of Pro.
Add to my gatewayOwn this server?
Sign in to claim this listing by proving control of its host.
Sponsor this listing
Pins it in a sponsor slot on the directory front page for 30 days, labelled Sponsored.
Sign in to sponsor · $39 / 30 daysStatus badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/nafafy-storefront)