Remote MCP · Endpoint

BEACON by Owner Connect MCP server

No. BEACON by Owner Connect answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://owners.virtualhangar.com/mcp/beacon

The last check completed an MCP handshake.

Registry name
com.virtualhangar.owners/beacon
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Ask about a private aircraft: approximate charter costs, trip requests and buyer inquiries.
Listing
From the official MCP registry (active).
Recent checks of BEACON by Owner Connect
CheckedResultHandshake
2 hours agoHandshake completed97 ms
1 day agoHandshake completed92 ms
4 days agoHandshake completed81 ms
6 days agoHandshake completed101 ms
9 days agoHandshake completed158 ms
11 days agoHandshake completed159 ms
13 days agoHandshake completed96 ms
15 days agoHandshake completed109 ms
17 days agoHandshake completed119 ms
19 days agoHandshake completed86 ms
20 days agoHandshake completed85 ms
22 days agoHandshake completed105 ms
23 days agoHandshake completed118 ms

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

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