Remote MCP · Endpoint

Vaaya MCP server

No. Vaaya answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://vaaya.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.vaaya/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
81 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Paid APIs and tokenized shares for agents. Prepaid funding, including authorized Instinct checkout.
Listing
From the official MCP registry (active).
Recent checks of Vaaya
CheckedResultHandshake
2 days agoHandshake completed81 ms
4 days agoHandshake completed96 ms
5 days agoHandshake completed74 ms
7 days agoHandshake completed64 ms
9 days agoHandshake completed83 ms
9 days agoHandshake completed70 ms
11 days agoHandshake completed87 ms
14 days agoHandshake completed56 ms
15 days agoHandshake completed104 ms
17 days agoHandshake completed78 ms
18 days agoHandshake completed130 ms
19 days agoHandshake completed76 ms
20 days agoHandshake completed63 ms
21 days agoHandshake completed103 ms
21 days agoHandshake completed74 ms
23 days agoHandshake completed85 ms
24 days agoHandshake completed81 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 Vaaya and makes no claim about it beyond what these checks measured.