Download PDFMarkdown Version

Connect Business Interruption Claim Log 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 disruption data into audit-ready insurance claim logs.

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.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

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 Business Interruption Claim Log capability set.

These are the exact actions your AI can choose when you ask it to work with Business Interruption Claim Log.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through Business Interruption Claim Log.

  1. 01

    Generate claim log

    This capability pulls all your reconciled data into a final, actionable audit trail. It organizes your findings into a chronological ledger for submission.

  2. 02

    Get claim period summary

    This capability identifies the active window for a claim. It uses your business disruption events to set the specific dates for indemnity.

  3. 03

    Reconcile revenue gap

    This capability calculates lost income. It compares your expected revenue against actual revenue to find the exact gap caused by the disruption.

  4. 04

    Calculate extra expenses

    This capability finds and totals the specific costs you incurred due to the disruption. It isolates these extra expenses from your standard operating costs.

One connector, every AI

Business Interruption Claim Log 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.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

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

You don't need a client to put Business Interruption Claim Log 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 Business Interruption Claim Log, so you can see the experience inside your AI.

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

Business Interruption Claim Log Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Business Interruption Claim Log capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "business-interruption-claim-log-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_Rnt0rMMa0m27NlTNVrsCu13fo8dG5NNFdRkFEke1/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 Business Interruption Claim Log

See all the AI clients this connector works with ↑

Who it's for

Built for the work Business Interruption Claim Log owners hand off.

This MCP is built for professionals managing financial recovery after business disruptions.

  • 01

    Forensic Accountants

    They hand off raw revenue and expense data to the AI to automate the reconciliation process.

  • 02

    Insurance Adjusters

    They use the generated logs to verify the validity of business interruption claims.

  • 03

    Business Owners

    They use the capabilities to quickly quantify their losses and prepare documentation for their insurers.

FAQ

Questions Business Interruption Claim Log owners ask.

  • 01

    What does this MCP do?

    This MCP automates forensic accounting for business interruption claims. It calculates lost revenue, identifies extra expenses, and builds an audit log.

  • 02

    Which AI clients can I use with this MCP?

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

  • 03

    How does it calculate lost revenue?

    It uses the reconcile_revenue_gap capability to compare your expected revenue against the actual revenue recorded during the disruption period.

  • 04

    Can it help with insurance documentation?

    Yes. The generate_claim_log capability creates a chronological, actionable ledger designed to meet insurance audit requirements.

  • 05

    Do I need to host the MCP myself?

    No. Vinkius hosts and manages the MCP for you. You just connect your client and start working.

  • 06

    How does the capability determine the claim period?

    The get_claim_period_summary capability calculates the intersection between the actual business closure dates and the policy's indemnity period.

  • 07

    What is a collection action?

    A collection action is a specific instruction generated by generate_claim_log to retrieve missing evidence, such as a vendor receipt, needed to substantiate a claim entry.

  • 08

    Can I use this with Claude Desktop?

    Yes, this MCP server can be connected to Claude Desktop, Cursor, VS Code, Windsurf, and any other MCP-compatible client via Vinkius Edge.

Explore

More in Finance

Suggestions

Connect Business Interruption Claim Log to Claude, Cursor, ChatGPT & more