com.jpyc-service/ec-storefront
REMOTE · EC.JPYC-SERVICE.COM
JPYC (JPY stablecoin) EC platform MCP: product search, x402 gasless checkout, order status.
Available components
Last scanned (10 hours ago)
Scores higher than 66% 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 Security63
- 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 9 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 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 Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1811 tokens (~201/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 Management93
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "authorize_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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
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.
- 26 Oct 26 +51
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 25 Oct 26 −51
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 24 Oct 26 −2
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 0.1.0 ▼ security
- Tool “get_order_status” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 90% ▼ functional
- “get_order_status” added a required parameter “message”, so existing callers break ▼ functional
- “get_order_status” added a required parameter “signature”, so existing callers break ▼ functional
- “get_order_status” added an optional parameter “offset” cosmetic
- “get_order_status” reworded the description of “customer_address” cosmetic
- 16 Oct 26 0
- “quote_checkout” reworded the description of “payer_address” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 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
- 25 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
- 20 Sept 26 0
- Tool “quote_checkout” rewrote its description, which is the text the model reads security
- Tool “submit_payment” rewrote its description, which is the text the model reads security
- “quote_checkout” added an optional parameter “demo_signature_version” cosmetic
- 19 Sept 26 0
- “quote_checkout” added an optional parameter “coupon_code” cosmetic
- “quote_checkout” added an optional parameter “idempotency_key” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
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://ec.jpyc-service.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ec.jpyc-service.com | CN=YR2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 59cbd3cb9b8928834356d71d39eaebf7b59 |
| SANs: ec.jpyc-service.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ec.jpyc-service.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jpyc-service.com. | absent | 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=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' 'wasm-unsafe-eval' https://platform.twitter.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https: wss:; frame-src 'self' https:; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self' https://dev.jpyc-service.com https://admin-ec.jpyc-service.com |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ec.jpyc-service.com/mcp | Verified | 200 | |
| http (plaintext) | http://ec.jpyc-service.com/mcp | HTTPS enforced | 308 | https://ec.jpyc-service.com/mcp |
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 →
authorize_transfer AAウォレット送金の事前承認 ~161
erc20-transfer 方式だけで、JPYC を送金する前に必ず呼ぶ。quote_checkout の選択した accept にある extra.payerAuthorization.message をウォレットで personal_sign し、その署名と reservation_id を渡す。サーバは EOA / ERC-1271 / ERC-6492 を検証して予約へ固定する。このツール自体は送金も approve も行わない。成功を確認してから accepted.amount ぴったりを transfer すること。eip3009 方式では呼ばない。
| Name | Type | Req | Description |
|---|---|---|---|
| reservation_id | string | yes | quote_checkout が返した reservation_id |
| signature | string | yes | payerAuthorization.message の personal_sign 署名 |
No output schema declared.
No examples provided.
get_order_status 注文状況の確認 ~86
購入履歴専用のSIWE署名で本人確認した注文履歴を最大50件返す。署名は一度だけ利用できる。
| Name | Type | Req | Description |
|---|---|---|---|
| customer_address | string | yes | – |
| message | string | yes | Purchase-history SIWE message; see the orders API authentication statement |
| offset | integer | – | – |
| signature | string | yes | – |
No output schema declared.
No examples provided.
get_product 商品詳細 ~99
1 つの商品の詳細を product_id で取得する。価格（JPYC 建て）・在庫・SKU・バリエーション・配送要否・対応チェーンを返す。購入の前に必ず呼んで、requires_shipping（配送先が必要か）と has_variants（オプション選択が必要か）を確認すること。
| Name | Type | Req | Description |
|---|---|---|---|
| product_id | string | yes | 商品 ID |
No output schema declared.
No examples provided.
get_shop ショップ詳細 ~80
1 つのショップ（生産者・職人）の詳細を slug で取得する。ショップのストーリーや説明、対応ブロックチェーン、x402 決済が有効かどうかを返す。
| Name | Type | Req | Description |
|---|---|---|---|
| shop_slug | string | yes | ショップの slug（URL 識別子） |
No output schema declared.
No examples provided.
list_products_in_shop ショップの商品一覧 ~89
1 つのショップの公開中の商品をすべて返す。価格（JPYC 建て）・在庫・バリエーション・配送要否・対応チェーンを含む。list_shops でショップを見つけたあと、その品揃えを見るのに使う。
| Name | Type | Req | Description |
|---|---|---|---|
| shop_slug | string | yes | ショップの slug |
No output schema declared.
No examples provided.
list_shops ショップ一覧 ~94
JPYC EC Platform に出店している公開ショップの一覧を返す。減農薬の農産物・地酒・伝統工芸品など、生産者から直接買えるショップが中心。各ショップの name / slug / 説明 / 対応チェーン / 商品点数を含む。商品を探す起点として最初に呼ぶとよい。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_checkout チェックアウト見積もり（x402 1回目） ~649
カートの内容で x402 チェックアウトの 1 回目を実行する。在庫を仮押さえし（有効期限は返り値 expires_at_unix_ms）、小計・割引・送料・合計（JPYC）と reservation_id、および PAYMENT-REQUIRED チャレンジ（base64url、x402 accepts 配列）を返す。accepts の決済方式: 『eip3009』(既定。通常購入の EOA ウォレットはこちらを選び、EIP-712 TransferWithAuthorization に署名する) と『erc20-transfer』(ecrecover 非対応のスマートコントラクトウォレット専用。payer_address を渡した予約にだけ提示される。extra.payerAuthorization.message を personal_sign して authorize_transfer を呼び、その成功後に表示額ぴったりの通常 ERC-20 transfer を実行し、txHash 任意/payerAddress 必須で submit_payment に渡す)。0円デモは demo_signature_version=1 と payer_address を渡すと demo-signature を提示する。送金せず personal_sign だけで完了する。全 item は同一ショップである必要がある。配送が必要な商品があれば shipping を、贈答なら gift_recipient を必ず渡すこと。
| Name | Type | Req | Description |
|---|---|---|---|
| coupon_code | string | – | ショップから受け取ったクーポンコード（任意。NFT割引との併用不可） |
| customer_email | string | yes | 注文確認メールの送信先（必須） |
| customer_note | string | – | 注文メモ |
| demo_signature_version | string | – | 0円デモのpersonal_signに対応する場合のみ指定 |
| gift_recipient | object | – | 贈り先（is_gift が true なら必須） |
| idempotency_key | string | – | 同じ見積もりの再試行で必ず再利用する一意キー。クーポン利用時は必須（UUID推奨）。異なる購入内容に同じキーを使わないこと |
| is_gift | boolean | – | 贈答かどうか |
| items | array | yes | 購入する商品 |
| payer_address | string | – | 支払いに使うウォレットアドレス（任意・推奨）。指定すると settle 時に支払いに使うウォレットと照合され、別ウォレットからの支払いは拒否される。スマートコントラクトウォレットで erc20-transfer 方式を使う場合は必須（指定が無いと accepts に erc20-transfer が提示されない） |
| preferred_chain_id | integer | – | 希望チェーン（任意。商品の対応チェーンから選ばれる） |
| shipping | object | – | 配送先（配送が必要な商品がある場合は必須） |
| shop_id | string | yes | ショップ ID（全 item 共通） |
No output schema declared.
No examples provided.
search_products 商品検索 ~246
JPYC EC Platform 上の公開商品を横断検索する。減農薬米・地酒・伝統工芸品など、生産者から直接 JPYC で購入できる商品が対象。text は自然言語のキーワード（例: 『丹波 米』）で、商品名と説明に部分一致する。category / tag（産地・認証種別など）、価格帯（min_price / max_price、JPYC）、shop_slug で絞り込める。売上順で最大 50 件返す。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 商品カテゴリーの完全一致 |
| limit | integer | – | 最大件数（1-50、既定 20） |
| max_price | number | – | 最高価格（JPYC） |
| min_price | number | – | 最低価格（JPYC） |
| shop_slug | string | – | 特定ショップに絞り込む |
| tag | string | – | 商品タグ（産地・認証種別など）の完全一致 |
| text | string | – | 自然言語のキーワード（商品名・説明に部分一致） |
No output schema declared.
No examples provided.
submit_payment 決済の確定（x402 2回目） ~307
quote_checkout で得た reservation_id と、エージェントが用意した x402 PaymentPayload（base64url）を渡して決済を確定する。demo-signatureならextra.payerAuthorization.messageをpersonal_signし、{payerAddress,demoSignature}を渡す。送金やauthorize_transferは呼ばない。quote_checkout の accepts から選んだ方式に応じて payload の中身が変わる: 『eip3009』なら { signature, authorization } (EIP-712 TransferWithAuthorization の署名)、『erc20-transfer』なら { payerAddress, txHash? } (ウォレットが実行した通常の ERC-20 transferの送金元アドレス。txHash は分かれば渡す任意ヒント — 無くてもサーバがon-chain のログを検索して照合する)。erc20-transfer は送金前に必ず authorize_transfer を成功させる。eip3009 はサーバが facilitator 経由で on-chain settle し、erc20-transfer はユーザーが既に送金したものをサーバが検証するだけ。いずれも確定した注文（order_number / tx_hash）を返す。
| Name | Type | Req | Description |
|---|---|---|---|
| payment_signature | string | yes | 署名済み x402 PaymentPayload（base64url JSON） |
| reservation_id | string | yes | quote_checkout が返した reservation_id |
No output schema declared.
No examples provided.
How do I install the com.jpyc-service/ec-storefront MCP server?
com.jpyc-service/ec-storefront is a hosted endpoint at https://ec.jpyc-service.com/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 · ec.jpyc-service.com
claude mcp add --transport http com-jpyc-service-ec-storefront 'https://ec.jpyc-service.com/mcp'
What is the com.jpyc-service/ec-storefront MCP server?
com.jpyc-service/ec-storefront is an MCP server listed in the public MCP registry as com.jpyc-service/ec-storefront. JPYC (JPY stablecoin) EC platform MCP: product search, x402 gasless checkout, order status. This page covers its hosted endpoint (https://ec.jpyc-service.com/mcp).
Is the com.jpyc-service/ec-storefront MCP server safe to use?
com.jpyc-service/ec-storefront 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 com.jpyc-service/ec-storefront MCP server expose?
com.jpyc-service/ec-storefront exposes 9 tools: list_shops, get_shop, list_products_in_shop, get_product, search_products, and 4 more. Their descriptions and schemas cost roughly 1,811 tokens of context every time the server is loaded.
Does the com.jpyc-service/ec-storefront MCP server require authentication?
No. We connected to com.jpyc-service/ec-storefront without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.jpyc-service/ec-storefront MCP server still maintained?
com.jpyc-service/ec-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.