How does the MCP count trip days?

The MCP uses inclusive calendar day counting, meaning it counts both the start and end dates as full days.

Can I compare two different trips?

Yes, you can use the compare_itineraries capability to determine which of two trips is longer.

What if my start and end dates are the same?

The MCP treats a trip where the start and end dates are identical as a valid 1-day itinerary.

Can this MCP check seasonal availability?

Yes, the validate_itinerary_range capability checks if your dates fall within specific allowed travel constraints.

Which AI clients can use this MCP?

You can use this MCP with any compatible client like Claude, Cursor, Windsurf, or VS Code.

How are the days counted?

The count is inclusive of both the arrival day and the departure day. For example, arriving Monday and leaving Tuesday is a 2-day itinerary.

What date format should I use?

All dates must follow the standard ISO 8601 calendar format.

Download PDF Markdown Version

Connect Itinerary Day Count to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Get precise trip durations and date validations instantly.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

How Vinkius works: one connection, every tool, in any AI

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Complete set · 4 capabilities

The complete Itinerary Day Count capability set.

These are the exact actions your AI can choose when you ask it to work with Itinerary Day Count.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Itinerary Day Count.

01
Compare itineraries
This capability compares the lengths of two different itineraries. It tells you exactly which trip is longer.
02
Get itinerary duration
This capability calculates the total number of inclusive calendar days for a single trip.
03
Get itinerary summary
This capability provides a detailed breakdown of the temporal footprint for your planned trip.
04
Validate itinerary range
This capability checks if your chosen date range stays within a specific set of allowed travel constraints.

One connector, every AI

Itinerary Day Count works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Itinerary Day Count to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1132ms average. Fast in production.

Itinerary Day Count is checked daily against the live service.

Daily averagePeak 1155ms

Sep 24Today

Fastest day: 1097ms
Slowest day: 1155ms
14-day trend: Stable+2%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Itinerary Day Count, so you can see the experience inside your AI.

It does not authenticate your account with Itinerary Day Count. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Itinerary Day Count Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_yGvJUyE6hVroNhjlfur6kLEQsXn4srlb1xqw9dAB/mcp

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — Itinerary Day Count capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "itinerary-day-count-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_yGvJUyE6hVroNhjlfur6kLEQsXn4srlb1xqw9dAB/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? How to give Claude access to Itinerary Day Count

See all the AI clients this connector works with ↑

Who it's for

Built for the work Itinerary Day Count owners hand off.

This MCP is built for anyone managing complex travel schedules through an AI interface.

01
Travel Planners
They hand off date math and itinerary comparisons to the AI.
02
Logistics Coordinators
They use the capability to validate that trips stay within specific time constraints.
03
Personal Assistants
They use the MCP to quickly summarize trip durations for clients.

FAQ

Questions Itinerary Day Count owners ask.

01
How does the MCP count trip days?
The MCP uses inclusive calendar day counting, meaning it counts both the start and end dates as full days.
02
Can I compare two different trips?
Yes, you can use the compare_itineraries capability to determine which of two trips is longer.
03
What if my start and end dates are the same?
The MCP treats a trip where the start and end dates are identical as a valid 1-day itinerary.
04
Can this MCP check seasonal availability?
Yes, the validate_itinerary_range capability checks if your dates fall within specific allowed travel constraints.
05
Which AI clients can use this MCP?
You can use this MCP with any compatible client like Claude, Cursor, Windsurf, or VS Code.
06
How are the days counted?
The count is inclusive of both the arrival day and the departure day. For example, arriving Monday and leaving Tuesday is a 2-day itinerary.
07
What date format should I use?
All dates must follow the standard ISO 8601 calendar format.

Explore

More in Productivity

Connect Itinerary Day Count to Claude, Cursor, ChatGPT & more

Connect Itinerary Day Count to ChatGPT, Claude and Gemini

Your AI does the work. We keep it safe and sound.