Remote MCP · Endpoint

Vaeo AI Discovery Reports MCP server

No. Vaeo AI Discovery Reports answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vaeo.com.au/mcp

The last check completed an MCP handshake.

Registry name
au.com.vaeo/reports
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
114 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
How often AI assistants name a local Australian business, and which pages they read.
Listing
From the official MCP registry (active).
Recent checks of Vaeo AI Discovery Reports
CheckedResultHandshake
1 hour agoHandshake completed114 ms
13 hours agoHandshake completed151 ms
1 day agoHandshake completed68 ms
2 days agoHandshake completed60 ms
4 days agoHandshake completed79 ms
5 days agoHandshake completed66 ms
5 days agoHandshake completed65 ms
7 days agoHandshake completed76 ms
9 days agoHandshake completed78 ms
12 days agoHandshake completed92 ms
14 days agoHandshake completed86 ms
16 days agoHandshake completed64 ms
18 days agoHandshake completed64 ms
20 days agoHandshake completed78 ms
22 days agoHandshake completed74 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 Vaeo AI Discovery Reports and makes no claim about it beyond what these checks measured.