Remote MCP · Endpoint

FareDice MCP server

No. FareDice answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://faredice.com/mcp

The last check completed an MCP handshake.

Registry name
com.faredice/trips
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
464 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Cheap multi-country trips and non-stop fares by day in Europe and Southeast Asia
Website
https://faredice.com/how
Listing
From the official MCP registry (active).
Recent checks of FareDice
CheckedResultHandshake
1 hour agoHandshake completed464 ms
2 days agoHandshake completed64 ms
5 days agoHandshake completed106 ms
7 days agoHandshake completed108 ms
9 days agoHandshake completed170 ms
11 days agoHandshake completed64 ms
13 days agoHandshake completed51 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed46 ms
18 days agoHandshake completed210 ms
20 days agoHandshake completed248 ms
21 days agoHandshake completed572 ms
23 days agoHandshake completed173 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with FareDice and makes no claim about it beyond what these checks measured.