Remote MCP · Endpoint
app.aplusz/flight-fares MCP server
No. app.aplusz/flight-fares answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://aplusz.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.aplusz/flight-fares
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 114 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Cheapest observed fare, 6-month low and best departure date for a city pair.
- Website
- https://aplusz.app/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 114 ms |
| 10 hours ago | Handshake completed | 126 ms |
| 1 day ago | Handshake completed | 103 ms |
| 2 days ago | Handshake completed | 72 ms |
| 4 days ago | Handshake completed | 74 ms |
| 4 days ago | Handshake completed | 120 ms |
| 5 days ago | Handshake completed | 75 ms |
| 6 days ago | Handshake completed | 93 ms |
| 8 days ago | Handshake completed | 395 ms |
| 11 days ago | Handshake completed | 96 ms |
| 13 days ago | Handshake completed | 95 ms |
| 16 days ago | Handshake completed | 103 ms |
| 18 days ago | Handshake completed | 137 ms |
| 20 days ago | Handshake completed | 111 ms |
| 22 days ago | Handshake completed | 110 ms |
| 24 days ago | Handshake completed | 117 ms |
| 26 days ago | Handshake completed | 92 ms |
| 27 days ago | Handshake completed | 66 ms |
| 29 days ago | Handshake completed | 85 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 app.aplusz/flight-fares and makes no claim about it beyond what these checks measured.