Remote MCP · Endpoint

com.followontours/cricket-travel MCP server

No. com.followontours/cricket-travel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.followontours.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.followontours/cricket-travel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
353 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Bespoke sports travel: cricket, golf, rugby, polo and playing tours. Tour operator, ABTOT 5718.
Listing
From the official MCP registry (active).
Recent checks of com.followontours/cricket-travel
CheckedResultHandshake
1 hour agoHandshake completed353 ms
18 hours agoHandshake completed319 ms
2 days agoHandshake completed382 ms
3 days agoHandshake completed341 ms
4 days agoHandshake completed347 ms
5 days agoHandshake completed366 ms
6 days agoHandshake completed347 ms
7 days agoHandshake completed347 ms
10 days agoHandshake completed378 ms
13 days agoHandshake completed397 ms
15 days agoHandshake completed416 ms
17 days agoHandshake completed316 ms
19 days agoHandshake completed327 ms
21 days agoHandshake completed474 ms
23 days agoHandshake completed305 ms
25 days agoHandshake completed325 ms
27 days agoHandshake completed328 ms
28 days agoHandshake completed319 ms
29 days agoHandshake completed363 ms

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

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 com.followontours/cricket-travel and makes no claim about it beyond what these checks measured.