Remote MCP · Endpoint

Store Catalog MCP server

No. Store Catalog answered an MCP handshake 26 minutes ago.

UpLast checked 26 minutes ago

Server URL

https://storecatalog.agenttoolworks.com/mcp

The last check completed an MCP handshake.

Registry name
com.agenttoolworks/storecatalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
563 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Shopify and WooCommerce product catalogs for agents: list, search, full product with barcodes.
Listing
From the official MCP registry (active).
Recent checks of Store Catalog
CheckedResultHandshake
26 minutes agoHandshake completed563 ms
10 days agoHandshake completed429 ms
11 days agoHandshake completed570 ms
12 days agoHandshake completed566 ms
13 days agoHandshake completed691 ms
14 days agoHandshake completed594 ms
15 days agoHandshake completed748 ms
16 days agoHandshake completed398 ms
17 days agoHandshake completed469 ms
19 days agoHandshake completed903 ms
22 days agoHandshake completed485 ms
24 days agoHandshake completed939 ms
26 days agoHandshake completed497 ms
29 days agoHandshake completed410 ms

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

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.

Listing data comes from the official MCP registry. Glide is not affiliated with Store Catalog and makes no claim about it beyond what these checks measured.