Remote MCP · Endpoint

Ticketglide Ticketing Agent MCP server

No. Ticketglide Ticketing Agent answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://ticketglide.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.ticketglide/travel-guides
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
205 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
TicketGlide travel comparison and tickets: attraction and day-trip guides and tailored search links.
Listing
From the official MCP registry (active).
Recent checks of Ticketglide Ticketing Agent
CheckedResultHandshake
17 minutes agoHandshake completed205 ms
8 days agoHandshake completed158 ms
9 days agoHandshake completed150 ms
11 days agoHandshake completed107 ms
12 days agoHandshake completed112 ms
13 days agoHandshake completed117 ms
14 days agoHandshake completed315 ms
14 days agoHandshake completed220 ms
16 days agoHandshake completed118 ms
19 days agoHandshake completed529 ms
21 days agoHandshake completed349 ms
24 days agoHandshake completed121 ms
26 days agoHandshake completed204 ms
28 days agoHandshake completed129 ms

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

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