Remote MCP · Endpoint

logue-vintage.com MCP server

No. logue-vintage.com answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://mcp.yomitasu.jp/s/logue-vintage-com/mcp

The last check completed an MCP handshake.

Registry name
jp.yomitasu/logue-vintage-com
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
625 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
新潟市中央区・沼垂にある完全予約制の古着屋LOGUE(ローグ)(logue-vintage.com の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of logue-vintage.com
CheckedResultHandshake
10 hours agoHandshake completed625 ms
2 days agoHandshake completed681 ms
4 days agoHandshake completed608 ms
6 days agoHandshake completed609 ms
8 days agoHandshake completed600 ms
10 days agoHandshake completed1.40 s
12 days agoHandshake completed647 ms
13 days agoHandshake completed648 ms
15 days agoHandshake completed1.20 s
16 days agoHandshake completed610 ms
18 days agoHandshake completed655 ms
20 days agoHandshake completed654 ms
22 days agoHandshake completed658 ms
23 days agoHandshake completed645 ms

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

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 logue-vintage.com and makes no claim about it beyond what these checks measured.