How do I connect this MCP to my AI client?

You connect once through the Vinkius platform. Vinkius hosts the MCP and manages the connection so it is ready to use in Claude, Cursor, or Windsurf immediately.

Can this MCP handle different insurance providers?

Yes. The capability includes a validation step specifically designed to ensure your data matches the unique schemas required by different insurers.

What happens if I am missing a receipt?

The engine uses a specific capability to scan your results and identify exactly which expenses lack sufficient evidence for a claim.

Does this work with my existing travel itineraries?

Yes. The engine is designed to correlate individual expenses directly with the disruptions found in your itinerary.

Do I need to host the MCP myself?

No. Vinkius hosts and manages the MCP for you, so you don't have to worry about infrastructure or credentials.

How does the engine link expenses to disruptions?

The link_expenses_to_events capability validates that the receipt timestamp falls within the disruption window and matches the policy terms.

Can I check if my claim is ready to submit?

Yes, you can use summarize_claim_status to see if the claim is 'Ready' based on matched expenses and missing actions.

Download PDF Markdown Version

Connect Travel Claim Reconciliation Engine to your AI

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. Turn messy travel receipts into ready-to-submit insurance claims.

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 Travel Claim Engine capability set.

These are the exact actions your AI can choose when you ask it to work with Travel Claim Engine.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Travel Claim Engine.

01
Link expenses to events
This capability matches your individual expenses to specific itinerary disruptions while checking them against policy rules.
02
Summarize claim status
Use this to get a high-level view of your claim's total value, progress, and readiness for submission.
03
Validate claim fields
This capability checks your organized claim data against the specific structure required by an insurer's form.
04
Identify missing documentation
This capability scans your matched expenses to find any valid costs that lack the necessary evidence for a claim.

One connector, every AI

Travel Claim Engine 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 Travel Claim Engine 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.

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 Travel Claim Engine, so you can see the experience inside your AI.

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

Travel Claim Engine Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_LDKSJ1sDQlyTQEKxhsxBzbVwVM4ctF8MJ9giTvHT/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 — Travel Claim Engine capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "travel-claim-reconciliation-engine-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_LDKSJ1sDQlyTQEKxhsxBzbVwVM4ctF8MJ9giTvHT/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 Travel Claim Engine

See all the AI clients this connector works with ↑

Who it's for

Built for the work Travel Claim Engine owners hand off.

This MCP is built for professionals handling high volumes of travel-related financial data and insurance filings.

01
Corporate Travel Managers
They hand off expense logs and itineraries to the AI to prepare bulk claims.
02
Insurance Adjusters
They use the engine to quickly verify if a claimant's expenses align with their policy.
03
Finance Operations Specialists
They use the capability to reconcile company travel spend against insurance recoveries.

FAQ

Questions Travel Claim Engine owners ask.

01
How do I connect this MCP to my AI client?
You connect once through the Vinkius platform. Vinkius hosts the MCP and manages the connection so it is ready to use in Claude, Cursor, or Windsurf immediately.
02
Can this MCP handle different insurance providers?
Yes. The capability includes a validation step specifically designed to ensure your data matches the unique schemas required by different insurers.
03
What happens if I am missing a receipt?
The engine uses a specific capability to scan your results and identify exactly which expenses lack sufficient evidence for a claim.
04
Does this work with my existing travel itineraries?
Yes. The engine is designed to correlate individual expenses directly with the disruptions found in your itinerary.
05
Do I need to host the MCP myself?
No. Vinkius hosts and manages the MCP for you, so you don't have to worry about infrastructure or credentials.
06
How does the engine link expenses to disruptions?
The link_expenses_to_events capability validates that the receipt timestamp falls within the disruption window and matches the policy terms.
07
Can I check if my claim is ready to submit?
Yes, you can use summarize_claim_status to see if the claim is 'Ready' based on matched expenses and missing actions.

Explore

More in Finance

Connect Travel Claim Engine to Claude, Cursor, ChatGPT & more

Connect Travel Claim Reconciliation Engine to your AI

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