Cheapest observed fare, 6-month low and best departure date for a city pair.
app.aplusz/flight-fares is a remote MCP server published at aplusz.app. It has been probed 6 times since 9/14/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 1,041 ms, a delay an agent will notice. It offers a narrow, focused set of 3 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
find_cheapest_fare — Description is incomplete and ends abruptly, missing critical parameter details.list_routes_from — Optional 'limit' parameter lacks clarification on default behavior.Risk: low
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
find_cheapest_fareReturns the cheapest observed one-way fare between two cities, plus the six-month low and the departure date on which the low was observed. Use whenever the user names an origin and a destination and asks about price, the cheapest date to fly, or whether a fare is a good deal. Both arguments are required; neither alone produces a valid answer. Answers are directional and per pair - PAR to BKK is not BKK to PAR and is not PAR to SIN. Prices are cached snapshots, never live quotes: say "last observed", never "current price", and surface live_check_url to any user about to book.
fromstringrequiredtostringrequiredlist_routes_fromReturns destinations reachable from one origin, sorted cheapest first. Use when the user asks where they can fly cheaply from a city, or wants inspiration rather than one specific pair. One call replaces dozens of page fetches. Prices are cached snapshots.
fromstringrequiredlimitintegerresolve_cityTurns a spoken city name into the uppercase IATA city code the other tools expect. Call this before find_cheapest_fare whenever you are not certain of a code. Do not invent codes.
querystringrequiredDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/app-aplusz-flight-fares)<a href="https://mcpmetrics.io/servers/app-aplusz-flight-fares"><img src="https://mcpmetrics.io/badge/app.aplusz/flight-fares/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Compare observed BC Ferries fares and dates, read qualified predictions, and manage fare alerts.
yesterday/today/tomorrow from a UTC date
UTC ISO ordinal date
Days in the current UTC month
Retry-After integer-or-date, value discarded
Days to pad current UTC month to 31
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-14 14:41:53 | Legacy | 200 | 902 | 200 | 915 | 2025-11-25 |
| 2026-09-14 12:38:15 | Legacy | 200 | 1041 | 200 | 1068 | 2025-11-25 |
| 2026-09-14 10:35:25 | Legacy | 200 | 1969 | 200 | 1940 | 2025-11-25 |
| 2026-09-14 08:31:43 | Legacy | 200 | 1000 | 200 | 999 | 2025-11-25 |
| 2026-09-14 06:26:32 | Legacy | 200 | 3755 | 200 | 3739 | 2025-11-25 |
| 2026-09-14 04:24:59 | Legacy | 200 | 809 | 200 | 880 | 2025-11-25 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.