Remote MCP · Endpoint

Folsn Product Catalog MCP server

No. Folsn Product Catalog answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.folsn.com/public/mcp

The last check completed an MCP handshake.

Registry name
com.folsn.mcp/own-store-products
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
608 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free read-only Korean product data: own-store sale terms, public seller listings, cosmetic records.
Listing
From the official MCP registry (active).
Recent checks of Folsn Product Catalog
CheckedResultHandshake
1 hour agoHandshake completed608 ms
3 days agoHandshake completed592 ms
12 days agoHandshake completed542 ms
12 days agoHandshake completed552 ms
14 days agoHandshake completed542 ms
15 days agoHandshake completed544 ms
16 days agoHandshake completed607 ms
17 days agoHandshake completed547 ms
18 days agoHandshake completed968 ms
19 days agoHandshake completed582 ms
22 days agoHandshake completed541 ms
25 days agoHandshake completed547 ms
27 days agoHandshake completed745 ms

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

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 Folsn Product Catalog and makes no claim about it beyond what these checks measured.