Remote MCP · Endpoint

com.jpyc-service/ec-storefront MCP server

No. com.jpyc-service/ec-storefront answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ec.jpyc-service.com/mcp

The last check completed an MCP handshake.

Registry name
com.jpyc-service/ec-storefront
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
285 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
JPYC (JPY stablecoin) EC platform MCP: product search, x402 gasless checkout, order status.
Website
https://ec.jpyc-service.com/
Listing
From the official MCP registry (active).
Recent checks of com.jpyc-service/ec-storefront
CheckedResultHandshake
1 hour agoHandshake completed285 ms
2 days agoHandshake completed356 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed97 ms
7 days agoHandshake completed481 ms
8 days agoHandshake completed160 ms
9 days agoHandshake completed89 ms
12 days agoHandshake completed78 ms
13 days agoHandshake completed161 ms
15 days agoHandshake completed88 ms
16 days agoHandshake completed69 ms
17 days agoHandshake completed210 ms
18 days agoHandshake completed1.03 s
19 days agoHandshake completed156 ms
20 days agoHandshake completed1.06 s
21 days agoHandshake completed73 ms
22 days agoHandshake completed108 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.jpyc-service/ec-storefront and makes no claim about it beyond what these checks measured.