Remote MCP · Endpoint

Your Travel Radar MCP server

No. Your Travel Radar answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://yourtravelradar.com/mcp

The last check completed an MCP handshake.

Registry name
com.yourtravelradar/night-trains
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Dated, sourced facts on European night train stations and lines, and measured punctuality.
Listing
From the official MCP registry (active).
Recent checks of Your Travel Radar
CheckedResultHandshake
1 hour agoHandshake completed84 ms
12 hours agoHandshake completed337 ms
1 day agoHandshake completed112 ms
2 days agoHandshake completed74 ms
4 days agoHandshake completed103 ms
4 days agoHandshake completed74 ms
5 days agoHandshake completed86 ms
7 days agoHandshake completed79 ms
8 days agoHandshake completed65 ms
11 days agoHandshake completed90 ms
13 days agoHandshake completed81 ms
16 days agoHandshake completed114 ms
18 days agoHandshake completed83 ms
20 days agoHandshake completed118 ms
22 days agoHandshake completed75 ms
24 days agoHandshake completed99 ms

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

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