Is the Jpyc Service Ec Storefront MCP server down?

mcp-registry/com.jpyc-service/ec-storefront · v0.1.0

As of 2026-10-26 19:05 UTC, the Jpyc Service Ec Storefront MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 12.8 hours.

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

Point your MCP client at this streamable-http endpoint: https://ec.jpyc-service.com/mcp

Agent-readiness: C (77/100)

What to fix (5)

Auto-fix: 9 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.jpyc-service%2Fec-storefront/fixes

{
  "name": "authorize_transfer",
  "description": "erc20-transfer 方式だけで、JPYC を送金する前に必ず呼ぶ。quote_checkout の選択した accept にある extra.payerAuthorization.message をウォレットで personal_sign し、その署名と reservation_id を渡す。サーバは EOA / ERC-1271 / ERC-6492 を検証して予約へ固定する。このツール自体は送金も approve も行わない。成功を確認してから accepted.amount ぴったりを transfer すること。eip3009 方式では呼ばない。",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "reservation_id",
      "signature"
    ],
    "properties": {
      "signature": {
        "type": "string",
        "pattern": "^0x(?:[0-9a-fA-F]{2})+$",
        "maxLength": 65538,
        "minLength": 4,
        "description": "payerAuthorization.message の personal_sign 署名"
      },
      "reservation_id": {
        "type": "string",
        "pattern": "^res_[0-9a-f]{32}$",
        "description": "quote_checkout が返した reservation_id"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "AAウォレット送金の事前承認"
}

{
  "name": "get_order_status",
  "description": "購入履歴専用のSIWE署名で本人確認した注文履歴を最大50件返す。署名は一度だけ利用できる。",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "customer_address",
      "message",
      "signature"
    ],
    "properties": {
      "offset": {
        "type": "integer",
        "maximum": 10000,
        "minimum": 0
      },
      "message": {
        "type": "string",
        "maxLength": 8192,
        "description": "Purchase-history SIWE message; see the orders API authentication statement"
      },
      "signature": {
        "type": "string",
        "maxLength": 4096
      },
      "customer_address": {
        "type": "string",
        "pattern": "^0x[a-fA-F0-9]{40}$"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "注文状況の確認"
}

{
  "name": "get_product",
  "description": "1 つの商品の詳細を product_id で取得する。価格（JPYC 建て）・在庫・SKU・バリエーション・配送要否・対応チェーンを返す。購入の前に必ず呼んで、requires_shipping（配送先が必要か）と has_variants（オプション選択が必要か）を確認すること。",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "product_id"
    ],
    "properties": {
      "product_id": {
        "type": "string",
        "minLength": 1,
        "description": "商品 ID"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "商品詳細"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.jpyc-service/ec-storefront"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.jpyc-service/ec-storefront"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~2,071 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.85% uptime over 30 days.

Largest tool definitions

• quote_checkout ~811 tokens
• submit_payment ~259 tokens
• search_products ~234 tokens
• authorize_transfer ~217 tokens
• get_order_status ~162 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jpyc-service%2Fec-storefront.svg)](https://glimind.com/server/mcp-registry%2Fcom.jpyc-service%2Fec-storefront?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.jpyc-service%2Fec-storefront?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jpyc-service%2Fec-storefront.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.jpyc-service%2Fec-storefront.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.jpyc-service%2Fec-storefront?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:eeb3796e3b810787…, first seen 2026-10-23, included at leaf 52049 of 74,913. Version history · verify what your client received.

Tools (9)

• authorize_transfer
• get_order_status
• get_product
• get_shop
• list_products_in_shop
• list_shops
• quote_checkout
• search_products
• submit_payment

Compare: most reliable payments servers · most reliable ecommerce servers · most reliable search servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Jpyc Service Ec Storefront MCP server down right now?

As of 2026-10-26 19:05 UTC, the Jpyc Service Ec Storefront MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 12.8 hours.

How many tools does Jpyc Service Ec Storefront MCP server provide?

Jpyc Service Ec Storefront MCP server advertises 9 tools, including authorize_transfer, get_order_status, get_product, get_shop, list_products_in_shop.

How do I install Jpyc Service Ec Storefront MCP server?

Point your MCP client at this streamable-http endpoint: https://ec.jpyc-service.com/mcp

Is the Jpyc Service Ec Storefront MCP server safe to connect to an AI agent?

Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Jpyc Service Ec Storefront MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.