# com.jpyc-service/ec-storefront (remote · ec.jpyc-service.com)

JPYC (JPY stablecoin) EC platform MCP: product search, x402 gasless checkout, order status.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ec.jpyc-service.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-jpyc-service-ec-storefront/ec.md), [page](https://verifymcp.io/servers/com-jpyc-service-ec-storefront/ec)

## Channel facts

- Endpoint: `https://ec.jpyc-service.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 8 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1125 tokens (~140/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-jpyc-service-ec-storefront https://ec.jpyc-service.com/mcp
```

### Codex

```toml
[mcp_servers.com-jpyc-service-ec-storefront]
url = "https://ec.jpyc-service.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jpyc-service-ec-storefront": {
      "type": "remote",
      "url": "https://ec.jpyc-service.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-jpyc-service-ec-storefront --url https://ec.jpyc-service.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-jpyc-service-ec-storefront:
    url: "https://ec.jpyc-service.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-jpyc-service-ec-storefront": {
      "type": "http",
      "url": "https://ec.jpyc-service.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (8)

### `list_shops` (~94 tokens)

ショップ一覧

JPYC EC Platform に出店している公開ショップの一覧を返す。減農薬の農産物・地酒・伝統工芸品など、生産者から直接買えるショップが中心。各ショップの name / slug / 説明 / 対応チェーン / 商品点数を含む。商品を探す起点として最初に呼ぶとよい。

### `get_shop` (~80 tokens)

ショップ詳細

1 つのショップ（生産者・職人）の詳細を slug で取得する。ショップのストーリーや説明、対応ブロックチェーン、x402 決済が有効かどうかを返す。

Input parameters:

- `shop_slug` (string, required): ショップの slug（URL 識別子）

### `list_products_in_shop` (~89 tokens)

ショップの商品一覧

1 つのショップの公開中の商品をすべて返す。価格（JPYC 建て）・在庫・バリエーション・配送要否・対応チェーンを含む。list_shops でショップを見つけたあと、その品揃えを見るのに使う。

Input parameters:

- `shop_slug` (string, required): ショップの slug

### `get_product` (~99 tokens)

商品詳細

1 つの商品の詳細を product_id で取得する。価格（JPYC 建て）・在庫・SKU・バリエーション・配送要否・対応チェーンを返す。購入の前に必ず呼んで、requires_shipping（配送先が必要か）と has_variants（オプション選択が必要か）を確認すること。

Input parameters:

- `product_id` (string, required): 商品 ID

### `search_products` (~246 tokens)

商品検索

JPYC EC Platform 上の公開商品を横断検索する。減農薬米・地酒・伝統工芸品など、生産者から直接 JPYC で購入できる商品が対象。text は自然言語のキーワード（例: 『丹波 米』）で、商品名と説明に部分一致する。category / tag（産地・認証種別など）、価格帯（min_price / max_price、JPYC）、shop_slug で絞り込める。売上順で最大 50 件返す。

Input parameters:

- `category` (string): 商品カテゴリーの完全一致
- `limit` (integer): 最大件数（1-50、既定 20）
- `max_price` (number): 最高価格（JPYC）
- `min_price` (number): 最低価格（JPYC）
- `shop_slug` (string): 特定ショップに絞り込む
- `tag` (string): 商品タグ（産地・認証種別など）の完全一致
- `text` (string): 自然言語のキーワード（商品名・説明に部分一致）

### `quote_checkout` (~301 tokens)

チェックアウト見積もり（x402 1回目）

カートの内容で x402 チェックアウトの 1 回目を実行する。在庫を 5 分間仮押さえし、小計・割引・送料・合計（JPYC）と reservation_id、および署名対象の x402 PAYMENT-REQUIRED チャレンジ（base64url）を返す。エージェントはこのチャレンジを自分のウォレットで EIP-3009 TransferWithAuthorization 署名し、submit_payment に渡す。全 item は同一ショップである必要がある。配送が必要な商品があれば shipping を、贈答なら gift_recipient を必ず渡すこと。

Input parameters:

- `customer_email` (string, required): 注文確認メールの送信先（必須）
- `customer_note` (string): 注文メモ
- `gift_recipient` (object): 贈り先（is_gift が true なら必須）
- `is_gift` (boolean): 贈答かどうか
- `items` (array, required): 購入する商品
- `preferred_chain_id` (integer): 希望チェーン（任意。商品の対応チェーンから選ばれる）
- `shipping` (object): 配送先（配送が必要な商品がある場合は必須）
- `shop_id` (string, required): ショップ ID（全 item 共通）

### `submit_payment` (~139 tokens)

決済の確定（x402 2回目）

quote_checkout で得た reservation_id と、エージェントが署名した x402 PaymentPayload（base64url）を渡して決済を確定する。サーバは facilitator 経由で on-chain settle し、確定した注文（order_number / tx_hash）を返す。署名は quote_checkout が返した payment_required の 内容に対する EIP-3009 TransferWithAuthorization であること。

Input parameters:

- `payment_signature` (string, required): 署名済み x402 PaymentPayload（base64url JSON）
- `reservation_id` (string, required): quote_checkout が返した reservation_id

### `get_order_status` (~77 tokens)

注文状況の確認

ウォレットアドレスの注文履歴を新しい順で返す。x402 で購入した注文は即時に order_status=3（決済完了）となり tx_hash を持つ。

Input parameters:

- `customer_address` (string, required): 顧客のウォレットアドレス（0x...）

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-jpyc-service-ec-storefront/ec#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 67
- 2026-07-31: 67
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://ec.jpyc-service.com/mcp
- Website: https://ec.jpyc-service.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-jpyc-service-ec-storefront/ec/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jpyc-service-ec-storefront/ec/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-jpyc-service-ec-storefront/ec