Remote MCP · Endpoint

Aviado AI MCP server

No. Aviado AI answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://aviado.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.aviado/health
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
139 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Cited supplement evidence, biomarker effects, interaction checks and brand quality
Listing
From the official MCP registry (active).
Recent checks of Aviado AI
CheckedResultHandshake
10 hours agoHandshake completed139 ms
2 days agoHandshake completed1.41 s
4 days agoHandshake completed1.51 s
5 days agoHandshake completed797 ms
7 days agoHandshake completed287 ms
8 days agoHandshake completed1.58 s
9 days agoHandshake completed182 ms
12 days agoHandshake completed1.50 s
13 days agoHandshake completed1.22 s
15 days agoHandshake completed1.89 s
16 days agoHandshake completed1.45 s
17 days agoHandshake completed129 ms
18 days agoHandshake completed101 ms
19 days agoHandshake completed1.59 s
20 days agoHandshake completed166 ms
21 days agoHandshake completed1.65 s
23 days agoHandshake completed1.40 s

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