Remote MCP · Endpoint

Orbylon MCP server

No. Orbylon answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://orbylon.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.orbylon/readiness
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
95 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Check that a business proved who it is, read what it sells, and order straight from it.
Listing
From the official MCP registry (active).
Recent checks of Orbylon
CheckedResultHandshake
1 hour agoHandshake completed95 ms
2 days agoHandshake completed82 ms
4 days agoHandshake completed68 ms
5 days agoHandshake completed90 ms
7 days agoHandshake completed73 ms
8 days agoHandshake completed71 ms
9 days agoHandshake completed91 ms
12 days agoHandshake completed88 ms
13 days agoHandshake completed67 ms
15 days agoHandshake completed81 ms
16 days agoHandshake completed91 ms
17 days agoHandshake completed51 ms
18 days agoHandshake completed59 ms
19 days agoHandshake completed56 ms
20 days agoHandshake completed57 ms
21 days agoHandshake completed69 ms
22 days agoHandshake completed64 ms

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

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