# Business Interruption Claim Log AI Agent Connect

> Business Interruption Claim Log MCP automates the forensic accounting needed to reconcile business closures with revenue and expense records. Your AI client uses this MCP to define indemnity windows, calculate lost income, and aggregate disruption costs into a single, actionable ledger for insurance purposes.

## Overview
- **Category:** finance
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_Rnt0rMMa0m27NlTNVrsCu13fo8dG5NNFdRkFEke1/ai-agent-connect
- **Tags:** forensic-accounting, insurance-claims, business-interruption, audit-log, revenue-reconciliation

## Description

You can stop manually chasing spreadsheets to prove lost revenue. This MCP handles the heavy lifting of forensic accounting by connecting your business disruption data to insurance requirements. When a closure occurs, your AI client uses this MCP to pinpoint the exact indemnity window and compare what you expected to earn against what actually hit your bank account. It doesn't just stop at revenue; it also tracks the specific extra expenses you incurred because of the disruption. Once the math is done, the MCP organizes everything into a chronological audit trail. This ledger is ready for submission, complete with notes on any missing evidence you still need to collect. It turns a messy pile of disruption data into a structured, defensible claim.

## Tools

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

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

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

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

## Prompt Examples

**Prompt:** 
```
Calculate the active claim period for a closure from 2024-01-01 to 2024-01-10 with a policy covering 2024-01-01 to 2024-01-15.
```

**Response:** 
```
The active period is from 2024-01-01 to 2024-01-10, totaling 10 days of interruption within policy coverage.
```

**Prompt:** 
```
Compare expected revenue of 5000 against actual revenue of 3000 for the period 2024-02-01 to 2024-02-02.
```

**Response:** 
```
The total revenue loss for the period is 2000.
```

**Prompt:** 
```
Identify extra expenses of 500 for equipment rental on 2024-03-01 with a policy limit of 1000.
```

**Response:** 
```
Total extra expenses are 500, leaving a remaining policy capacity of 500.
```

## Capabilities

### Indemnity Window Mapping
Your agent uses this to match disruption dates against your insurance policy coverage.

### Revenue Gap Analysis
Your agent calculates the difference between projected earnings and actual income during a closure.

### Expense Aggregation
Your agent identifies specific costs that only occurred because of the business interruption.

### Audit Trail Generation
Your agent compiles all findings into a chronological ledger for insurance adjusters.

## Use Cases

### Natural Disaster Recovery
Quantify lost revenue and extra costs following a storm or flood that forced a facility closure.

### Supply Chain Disruptions
Calculate the financial impact when a vendor failure causes a temporary halt in production.

### Policy Compliance Audits
Verify that a claim falls within the specific indemnity windows defined by an insurance policy.

### Expense Verification
Isolate specific emergency costs from standard operating expenses to prove they are claimable.

## Benefits

- Reduces manual math errors by automating revenue and expense reconciliation.
- Shortens the time between a business disruption and a completed claim log.
- Creates a structured audit trail that follows insurance requirements.
- Identifies missing evidence needed to finalize a claim.

## How It Works

The process moves from raw data to a finished ledger through your AI client.

1. Connect your preferred MCP-compatible client to Vinkius.
2. Provide your disruption dates and revenue data to your agent.
3. The agent uses the MCP tools to calculate gaps and extra expenses.
4. The agent generates a final, chronological claim log for your review.

## Frequently Asked Questions

**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.

**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.

**How does it calculate lost revenue?**
It uses the reconcile_revenue_gap tool to compare your expected revenue against the actual revenue recorded during the disruption period.

**Can it help with insurance documentation?**
Yes. The generate_claim_log tool creates a chronological, actionable ledger designed to meet insurance audit requirements.

**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.

**How does the tool determine the claim period?**
The `get_claim_period_summary` tool calculates the intersection between the actual business closure dates and the policy's indemnity period.

**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.

**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.