Remote MCP · Endpoint

Viatsy MCP server

No. Viatsy answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://viatsy.com/mcp

The last check completed an MCP handshake.

Registry name
com.viatsy/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
441 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search Asia travel tours, browse guides, request quotes, find upcoming group departures.
Listing
From the official MCP registry (active).
Recent checks of Viatsy
CheckedResultHandshake
1 hour agoHandshake completed441 ms
2 days agoHandshake completed1.81 s
4 days agoHandshake completed429 ms
5 days agoHandshake completed579 ms
7 days agoHandshake completed475 ms
8 days agoHandshake completed508 ms
9 days agoHandshake completed614 ms
12 days agoHandshake completed403 ms
13 days agoHandshake completed562 ms
15 days agoHandshake completed1.33 s
16 days agoHandshake completed486 ms
17 days agoHandshake completed548 ms
18 days agoHandshake completed1.17 s
19 days agoHandshake completed665 ms
20 days agoHandshake completed850 ms
21 days agoHandshake completed501 ms
22 days agoHandshake completed729 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 Viatsy and makes no claim about it beyond what these checks measured.