// the take
A single Go binary that exposes real flight, hotel, train, and ferry search to any MCP-compatible AI client (Claude, Cursor, Codex, etc.) without requiring API keys for the default providers. It's for developers who want their AI assistant to actually search live travel data instead of guessing, by querying Google Flights/Hotels and 20+ ground-transport sources directly.
Collapsing the tool surface into one smart router with 66 aliases (claimed ~98.9% smaller tools/list payload) is a genuinely useful MCP design pattern that most multi-tool servers get wrong. It reports typed failure states per provider (AKAMAI_BLOCK, RATE_LIMITED, etc.) instead of returning an empty result dressed up as success, which matters a lot when an LLM is acting on the output unsupervised. The engineering discipline is real: atomic JSON writes, a transactional SQLite-backed watch store with pre-migration backups, cross-platform race testing, and a smoke test that runs the packaged binary before release.
By default it reads your browser's cookies (including macOS Keychain access) to bypass bot protection on hotel and rail sites — documented thoroughly, but it's still a local tool reusing your live sessions against third-party sites whose ToS likely prohibit automated access, which is a real liability for the end user, not just the maintainer. Core flight/hotel search leans on scraping Google Flights/Hotels and similar unofficial endpoints rather than real APIs, so it's structurally fragile to upstream changes and actively degrades from cloud/datacenter IPs (the README itself documents a run where several providers 403'd from a Kubernetes cluster). The price-watch feature is explicitly experimental and the README calls out a past bug where a lowered history limit was silently ignored during storage migration, meaning upgrades could delete data users thought was capped safely. It's PolyForm Noncommercial licensed, so anything beyond personal use requires a paid license, which rules out embedding it in most products despite the open repo.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →