Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Ec Storefront is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
JPYC (JPY stablecoin) EC platform MCP: product search, x402 gasless checkout, order status.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ec-storefront-mcp https://ec.jpyc-service.com/mcp
# 2 — ask your agent for something these tools do
# list_shops, get_shop, list_products_in_shop and 6 more
Ec Storefront costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ec-storefront-mcp https://ec.jpyc-service.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
JPYC EC Platform に出店している公開ショップの一覧を返す。減農薬の農産物・地酒・伝統工芸品など、生産者から直接買えるショップが中心。各ショップの name / slug / 説明 / 対応チェーン / 商品点数を含む。商品を探す起点として最初に呼ぶとよい。
No parameter schema on file.
1 つのショップ(生産者・職人)の詳細を slug で取得する。ショップのストーリーや説明、対応ブロックチェーン、x402 決済が有効かどうかを返す。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop_slug | string | yes | ショップの slug(URL 識別子) |
1 つのショップの公開中の商品をすべて返す。価格(JPYC 建て)・在庫・バリエーション・配送要否・対応チェーンを含む。list_shops でショップを見つけたあと、その品揃えを見るのに使う。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop_slug | string | yes | ショップの slug |
1 つの商品の詳細を product_id で取得する。価格(JPYC 建て)・在庫・SKU・バリエーション・配送要否・対応チェーンを返す。購入の前に必ず呼んで、requires_shipping(配送先が必要か)と has_variants(オプション選択が必要か)を確認すること。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | string | yes | 商品 ID |
JPYC EC Platform 上の公開商品を横断検索する。減農薬米・地酒・伝統工芸品など、生産者から直接 JPYC で購入できる商品が対象。text は自然言語のキーワード(例: 『丹波 米』)で、商品名と説明に部分一致する。category / tag(産地・認証種別など)、価格帯(min_price / max_price、JPYC)、shop_slug で絞り込める。売上順で最大 50 件返す。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | 自然言語のキーワード(商品名・説明に部分一致) |
| category | string | no | 商品カテゴリーの完全一致 |
| tag | string | no | 商品タグ(産地・認証種別など)の完全一致 |
| shop_slug | string | no | 特定ショップに絞り込む |
| min_price | number | no | 最低価格(JPYC) |
| max_price | number | no | 最高価格(JPYC) |
| limit | integer | no | 最大件数(1-50、既定 20) |
カートの内容で 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_transf
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop_id | string | yes | ショップ ID(全 item 共通) |
| items | array | yes | 購入する商品 |
| customer_email | string | yes | 注文確認メールの送信先(必須) |
| preferred_chain_id | integer | no | 希望チェーン(任意。商品の対応チェーンから選ばれる) |
| payer_address | string | no | 支払いに使うウォレットアドレス(任意・推奨)。指定すると settle 時に支払い元と照合され、別ウォレットからの支払いは拒否される。スマートコントラクトウォレットで erc20-transfer 方式を使う場合は必須(指定が無いと accepts に erc20-transfer が提示されない) |
| demo_signature_version | string | no | 0円デモのpersonal_signに対応する場合のみ指定 |
| shipping | object | no | 配送先(配送が必要な商品がある場合は必須) |
| is_gift | boolean | no | 贈答かどうか |
| gift_recipient | object | no | 贈り先(is_gift が true なら必須) |
| customer_note | string | no | 注文メモ |
| coupon_code | string | no | ショップから受け取ったクーポンコード(任意。NFT割引との併用不可) |
| idempotency_key | string | no | 同じ見積もりの再試行で必ず再利用する一意キー。クーポン利用時は必須(UUID推奨)。異なる購入内容に同じキーを使わないこと |
erc20-transfer 方式だけで、JPYC を送金する前に必ず呼ぶ。quote_checkout の選択した accept にある extra.payerAuthorization.message をウォレットで personal_sign し、その署名と reservation_id を渡す。サーバは EOA / ERC-1271 / ERC-6492 を検証して予約へ固定する。このツール自体は送金も approve も行わない。成功を確認してから accepted.amount ぴったりを transfer すること。eip3009 方式では呼ばない。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_id | string | yes | quote_checkout が返した reservation_id |
| signature | string | yes | payerAuthorization.message の personal_sign 署名 |
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? } (ウォレットが
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reservation_id | string | yes | quote_checkout が返した reservation_id |
| payment_signature | string | yes | 署名済み x402 PaymentPayload(base64url JSON) |
ウォレットアドレスの注文履歴を新しい順で返す。x402 で購入した注文は即時に order_status=3(決済完了)となり tx_hash を持つ。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_address | string | yes | 顧客のウォレットアドレス(0x...) |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ec Storefront or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Ec Storefront can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.