2027 eclipse costs: independent, not affiliated with IMXP (The Eclipse Missions, EclipseSeekers)
Scored across 6 tools
Most tools have clearly distinct scopes: get_destination is single-place depth, compare_destinations is a 2-4 place side-by-side, list_eclipse_sites is explicitly non-priced points rather than destinations. The main overlap is between list_destinations (all places, ranked summary) and plan_trip (ranked places for one traveller with passport/fares), which could be confused at a glance, though descriptions attempt to differentiate.
All six tools follow a clean verb_noun snake_case pattern: compare_destinations, get_destination, get_flights, list_destinations, list_eclipse_sites, plan_trip. The list_/get_/compare_ prefixes align with the operation semantics consistently.
Six tools is well-scoped for an eclipse-travel data server: list, get, compare, plan, and flight lookup, each earning its place. No filler tools and no obvious missing primitive at the count level.
Coverage is solid: destination listing, detailed single lookup, comparison, eclipse-site geometry, flight fares, and per-traveller planning with passport entry regimes. Minor gaps exist, such as no standalone way to enumerate supported passports or query entry regimes independently, but agents can route these through get_destination or plan_trip.
The figures a choice between places turns on, for two to four destinations at once, in the order of the site's ranking whatever the order asked: totality and its times, lodging (eclipse-week mean, per person, Eclipse Premium, reading day), both ends of the cloud range, heat, access, airport, the cost of the observation, and the entry regime of one passport or of each passport we cover. get_destination has the rest.
Inputs: destinations (required), passport.
Everything EclipseMission holds on one place, each figure with its source and reading day: the eclipse (duration, and contact times where our oracle has them), lodging (eclipse week, week after, the two eclipse nights, solo traveller and hostels where measured, with the ten prices behind each mean), sky, heat, entry regime by passport, the cost of the observation itself, access and the airfares read to its airport.
Inputs: destination (required), passport.
The airfares EclipseMission has read, each dated and sourced. Two families that must never be added together: Google Flights searches (return trip, two adults, as the search displayed it) and easyJet fares read at the airline (one seat, one way). Filter by departure airport, destination, or both. A route we have not read is absent, which is not a claim that no flight exists.
Inputs: origin, destination.
Every place EclipseMission has measured for the total solar eclipse of 2 August 2027, in the order of the site's ranking: the places every reader can go to, ranked by lodging price per person, cheapest first, then Mecca, priced but unranked (entry restricted to Muslims). For each: totality duration (our validated oracle), lodging for two adults over four nights, 31 July to 4 August 2027 (mean of the ten cheapest rooms, dated), the Eclipse Premium (that price over the same search a week later), cloud as a range of two reanalyses, heat, public-transport access, the nearest airport and our one-word verdict. Filters narrow the list; they never reorder it.
Inputs: country, min_totality_seconds, open_to_all_visitors, max_price_per_person_eur.
Points along the path of the 2 August 2027 eclipse for which our oracle computed totality once — towns, capes, peaks, monuments — with the cloud range of two reanalyses at each. Points, not destinations: nothing was priced there and no entry or access was read. Points outside the path carry no totality. No coordinates are taken: the list is fixed, and a place absent from it has not been computed.
Inputs: sort, country, in_path, max_cloud_pct, +1 more.
The destinations that fit one traveller, in the order of the site's ranking, each with its lodging figure, totality and sky, the entry regime of their passport, and the fares we have read from their airport to it. The fares and the stay are given side by side, never summed: they are different searches, read on different days. A place with no fare read from that airport is kept, with a note: that is a gap in our readings, not a claim that no flight exists.
Inputs: origin, country, passport, min_totality_seconds, +2 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Independent checks of paid x402 data sellers and of AI-agent access to shopping and travel sites
XRP research, paper arena and free XRPL transaction explanations / x402 diagnostics. No signing.
Paid remote MCP for spec driven development acceptance gate MCP, structured receipts, audit logs, an
ASIC solar/battery profit. Keyless MCP 20/min+200/day; paid 25/1k/10k/50k. Not financial advice.
Add one secure layer between your agents and this server.