Remote MCP · Endpoint

ESEO — карточки Wildberries, Ozon, Яндекс Маркет MCP server

No. ESEO — карточки Wildberries, Ozon, Яндекс Маркет answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://eseo.su/api/mcp

The last check completed an MCP handshake.

Registry name
su.eseo/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
400 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
SEO score and checks for Wildberries, Ozon, Yandex Market product cards; AI card generation.
Listing
From the official MCP registry (active).
Recent checks of ESEO — карточки Wildberries, Ozon, Яндекс Маркет
CheckedResultHandshake
3 days agoHandshake completed400 ms
3 days agoHandshake completed407 ms
4 days agoHandshake completed371 ms
6 days agoHandshake completed376 ms
7 days agoHandshake completed378 ms
8 days agoHandshake completed443 ms
9 days agoHandshake completed430 ms
10 days agoHandshake completed417 ms
11 days agoHandshake completed416 ms
14 days agoHandshake completed375 ms
17 days agoHandshake completed414 ms
19 days agoHandshake completed395 ms
21 days agoHandshake completed385 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 ESEO — карточки Wildberries, Ozon, Яндекс Маркет and makes no claim about it beyond what these checks measured.