Remote MCP · Endpoint

PoloPan Fashion MCP Server MCP server

No. PoloPan Fashion MCP Server answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://mcp-server.polopan.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.rofoso-com/polopan-fashion-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.02 s
Tools exposed
19 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fashion & apparel MCP: visual outfit search, stock verification, and 1-click checkout.
Listing
From the official MCP registry (active).
Recent checks of PoloPan Fashion MCP Server
CheckedResultHandshake
35 minutes agoHandshake completed1.02 s
9 days agoHandshake completed674 ms
10 days agoHandshake completed660 ms
11 days agoHandshake completed676 ms
12 days agoHandshake completed677 ms
14 days agoHandshake completed605 ms
14 days agoHandshake completed626 ms
15 days agoHandshake completed663 ms
17 days agoHandshake completed641 ms
19 days agoHandshake completed673 ms
21 days agoHandshake completed642 ms
24 days agoHandshake completed639 ms
26 days agoHandshake completed667 ms
28 days agoHandshake completed640 ms

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

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 PoloPan Fashion MCP Server and makes no claim about it beyond what these checks measured.