Remote MCP · Endpoint

space.lanitech.pc/pc-okaidoku-store MCP server

No. space.lanitech.pc/pc-okaidoku-store answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://pc.lanitech.space/api/mcp

The last check completed an MCP handshake.

Registry name
space.lanitech.pc/pc-okaidoku-store
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
123 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
PCお買い得ストア by lanitech — 法人・個人向けの特価PC・Mac・ディスプレイ・周辺機器カタログ。商品検索・価格確認・カテゴリ一覧(読み取り専用・税込JPY)。
Listing
From the official MCP registry (active).
Recent checks of space.lanitech.pc/pc-okaidoku-store
CheckedResultHandshake
36 minutes agoHandshake completed123 ms
3 days agoHandshake completed133 ms
13 days agoHandshake completed114 ms
14 days agoHandshake completed203 ms
15 days agoHandshake completed88 ms
16 days agoHandshake completed105 ms
17 days agoHandshake completed154 ms
18 days agoHandshake completed95 ms
19 days agoHandshake completed99 ms
20 days agoHandshake completed139 ms
22 days agoHandshake completed98 ms
25 days agoHandshake completed89 ms

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

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 space.lanitech.pc/pc-okaidoku-store and makes no claim about it beyond what these checks measured.