Remote MCP · Endpoint
io.tooloracle/flightoracle MCP server
No. io.tooloracle/flightoracle answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://tooloracle.io/flight/mcp/
The last check completed an MCP handshake.
- Registry name
- io.tooloracle/flightoracle
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 300 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 47.4% from 19 checks
- Described by its publisher as
- Flight Intelligence MCP — search, cheapest dates, multi-city, airline compare via Google Flights
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 300 ms |
| 12 hours ago | Handshake completed | 308 ms |
| 1 day ago | Handshake completed | 302 ms |
| 2 days ago | Handshake completed | 376 ms |
| 4 days ago | Handshake completed | 300 ms |
| 4 days ago | Handshake completed | 420 ms |
| 5 days ago | Handshake completed | 300 ms |
| 7 days ago | Handshake completed | 302 ms |
| 8 days ago | Handshake completed | 302 ms |
| 11 days ago | Failed - the connection was refused or dropped | — |
| 13 days ago | Failed - the connection was refused or dropped | — |
| 16 days ago | Failed - the connection was refused or dropped | — |
| 18 days ago | Failed - the connection was refused or dropped | — |
| 20 days ago | Failed - the connection was refused or dropped | — |
| 22 days ago | Failed - the connection was refused or dropped | — |
| 24 days ago | Failed - the connection was refused or dropped | — |
| 26 days ago | Failed - the connection was refused or dropped | — |
| 28 days ago | Failed - the connection was refused or dropped | — |
| 29 days ago | Failed - the connection was refused or dropped | — |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 io.tooloracle/flightoracle and makes no claim about it beyond what these checks measured.