Plan Schengen short stays with a rolling 90/180 rule calculator and a daily CSV download.
Scored across 3 tools
calculate_schengen_days is clearly the past/present compliance check, while find_schengen_reset_dates and plan_schengen_trip both project future availability and could be confused at a glance. The descriptions do draw the line (per-date headroom vs. max consecutive stay), so the overlap is manageable.
All three follow a snake_case verb_noun pattern (calculate_/find_/plan_ + domain noun), so the convention is predictable. The minor wrinkle is that the domain token appears in different shapes ('schengen_days' vs 'schengen_reset_dates' vs 'schengen_trip'), but this is still readable and consistent enough.
Three tightly scoped tools map cleanly onto the three natural questions of a Schengen calculator: current position, future headroom, and trip planning. Nothing feels padded or missing at the count level.
The surface covers status check, forward-looking headroom, and trip length planning, which is the core lifecycle for this domain. Gaps are mostly explicit non-goals (bilateral agreements, permits, long-stay visas), though there is no tool for validating or explaining a specific overstay or aggregating multiple travelers, which agents may occasionally want.
Use this when the user needs a schengen calculator, schengen days left, schengen overstay dates or a 90/180 rule calculator for past and planned short stays. Returns days used and left on the check date, stay compliance, overstay dates and daily CSV. Accepts ISO or English US text dates, up to 60 stays over 1,100 days, years 1900–2100. Open stays end at the check date; touching stays merge. Does not model bilateral agreements, residence permits, long-stay visas or visa-sticker limits; calculation aid, not legal advice.
Inputs: stays (required), check_date (required). Returns: kind, note, notes, days_left, +12 more
Use this when the user wants schengen days left to return, a schengen 90 day rule projection or a days in Europe calculator for future availability. Projects window headroom on the next 180 dates with a daily CSV, assuming no further stays and departure by the reference date. Up to 60 stays over 1,100 days, years 1900–2100. Reference date defaults to America/New_York today. Headroom is not maximum consecutive trip length. Does not model bilateral agreements, residence permits, long-stay visas or visa-sticker limits; not legal advice.
Inputs: past_stays (required), reference_date. Returns: kind, note, notes, days_left, +7 more
Use this when the user asks how many days can I stay in Europe, wants a schengen visa calculator or needs to plan 90 days in 180 days. Finds the maximum consecutive short stay from an entry date and the first entry that supports a requested length. Past stays must be closed and end by entry; up to 60 stays over 1,100 days, years 1900–2100, requested lengths 1–90 days. Does not authorize entry or model bilateral agreements, residence permits, long-stay visas or visa-sticker limits; not legal advice.
Inputs: entry_date (required), past_stays (required), planned_length. Returns: kind, note, notes, downloads, +8 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Schengen 90/180-day calculator, earliest re-entry date and ETIAS check. Stateless, no data stored.
Schengen 90/180 rolling-window calculator MCP server: stay math, trip checks, rule explainer.
Travel ledger for AI: journeys, stays, expenses, tax-residency day counts and Schengen 90/180.
Plan trips and track visa days per traveller across 39,601 entry rules
Add one secure layer between your agents and this server.