Remote MCP · Endpoint

Orlandu's Arcade MCP server

No. Orlandu's Arcade answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.orlandu.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.orlandu/arcade
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
228 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read-only tools for orlandu.com: site search, pages, Sony PVM/BVM specs, PlayChoice-10 library.
Listing
From the official MCP registry (active).
Recent checks of Orlandu's Arcade
CheckedResultHandshake
2 hours agoHandshake completed228 ms
1 day agoHandshake completed572 ms
3 days agoHandshake completed59 ms
3 days agoHandshake completed129 ms
4 days agoHandshake completed60 ms
5 days agoHandshake completed58 ms
7 days agoHandshake completed545 ms
10 days agoHandshake completed90 ms
12 days agoHandshake completed523 ms
15 days agoHandshake completed478 ms
17 days agoHandshake completed467 ms
19 days agoHandshake completed76 ms
21 days agoHandshake completed81 ms
23 days agoHandshake completed565 ms
25 days agoHandshake completed65 ms

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

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 Orlandu's Arcade and makes no claim about it beyond what these checks measured.