Remote MCP · Endpoint

XRメモランダム MCP server

No. XRメモランダム answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.yomitasu.jp/s/orecen-com/mcp

The last check completed an MCP handshake.

Registry name
jp.yomitasu/orecen-com
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
583 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
XR(AR/VR/MR)に関する情報をメインに扱うサイトです。(orecen.com の内容を検索して答える。ヨミタス経由)
Listing
From the official MCP registry (active).
Recent checks of XRメモランダム
CheckedResultHandshake
43 minutes agoHandshake completed583 ms
9 days agoHandshake completed231 ms
10 days agoHandshake completed217 ms
11 days agoHandshake completed283 ms
12 days agoHandshake completed205 ms
14 days agoHandshake completed222 ms
15 days agoHandshake completed224 ms
15 days agoHandshake completed213 ms
17 days agoHandshake completed229 ms
19 days agoHandshake completed386 ms
21 days agoHandshake completed223 ms
24 days agoHandshake completed241 ms
26 days agoHandshake completed229 ms
28 days agoHandshake completed657 ms

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

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 XRメモランダム and makes no claim about it beyond what these checks measured.